Skip to content
VulniPulse
Advisory severityHigh8.8Red Hat Linux

High [CVE-2026-92867] arbitrary code execution via out-of-bounds write

This high-severity Red Hat Linux advisory covers CVE-2026-92867.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-92867 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Red Hat LinuxUnclassified
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

arbitrary code execution via out-of-bounds write. Red Hat rates this important (CVSS 8.8).

Weakness: CWE-787.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Disable the Pgpool-II service if it is not required in your environment: 1. Stop and disable the service: # systemctl stop pgpool # systemctl disable pgpool Alternatively, if the service must remain operational, restrict network access to trusted database clients using firewalld: 2. Allow access only from trusted IP addresses or subnets: # firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<trusted_ip_or_subnet>" port port="9999" protocol="tcp" accept' 3. Ensure general access to the service port is removed: # firewall-cmd --permanent --remove-port=9999/tcp 4. Apply the changes: # firewall-cmd --reload Caveats: Stopping the service disables PostgreSQL connection pooling and load balancing capabilities. Restricting network access with firewall rules will block any legitimate clients connecting from unlisted IP addresses. Warning: Stopping the pgpool service or reloading firewall configurations will disconnect existing client database connections and disrupt service availability until clients reconnect.

Official advisory · high-confidence parse· fetched 4 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.