How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is high, an attacker needs no privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality low, integrity none, availability low.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:L
- Attack vector: Network — reachable from anywhere that can route to the service.
- Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
- Privileges required: None — an unauthenticated stranger can try it.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
- Integrity impact: None.
- Availability impact: Low — limited, and the attacker does not choose what is affected.
Weakness class
CVE-2026-12549 is classified as CWE-805: Buffer Access with Incorrect Length Value. The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.
Affected software
CVE-2026-12549 is recorded against 2 packages.
Timeline and source
Published on 22 June 2026 and last revised on 8 July 2026. A public exploit is known to exist, which raises the urgency of patching considerably. A vendor advisory or fix has been published. Record sourced from NVD.
References
access.redhat.com
access.redhat.com
bugzilla.redhat.com
gitlab.gnome.org
Other advisories for this package
enterprise-linux has other advisories on record. If you are patching this one, these are worth checking on the same host:
Same weakness in other software
These advisories are the same class of weakness (CWE-805: Buffer Access with Incorrect Length Value) in other software:
