Low [CVE-2026-14685] Local state issue via 'Count' argument manipulation
This low-severity Red Hat Linux advisory covers CVE-2026-14685 affecting Red Hat Hardened Images, Red Hat Ansible Automation Platform 2, Red Hat Enterprise Linux 8.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Summary
A vulnerability has been found in HdrHistogram up to 2.2.2. This vulnerability affects the function recordValueWithCount of the file src/main/java/org/HdrHistogram/AbstractHistogram.java of the component AbstractHistogram.
Such manipulation of the argument Count leads to state issue. The attack can only be performed from a local environment.
The exploit has been disclosed to the public and may be used. The existence of this vulnerability is still disputed at present.
This issue is disputed due to the potential lack of crossing of security boundaries and the pre-requisites for a successful attack. A flaw was found in HdrHistogram.
A local attacker could exploit this vulnerability by manipulating the 'Count' argument within the `recordValueWithCount` function. This manipulation leads to a state issue, which could impact the integrity of data processing within the affected component.
This flaw in HdrHistogram is rated as Low impact. Exploitation requires local access to the system where HdrHistogram is used.
Red Hat severity: Low — CVSS 3.3 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N). Weakness: CWE-1284.
Affected Red Hat products: Red Hat Hardened Images; Red Hat Ansible Automation Platform 2; Red Hat Enterprise Linux 8; Red Hat OpenShift AI (RHOAI).
Affected products named by the advisory: Red Hat package: hdrhistogram.
Is CVE-2026-14685 exploited?
No exploitation is reported in the sources VulniPulse tracks: CVE-2026-14685 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.
How do I fix CVE-2026-14685?
Upgrade to a fixed release named by Red Hat:
- netavark-main-2.0.0-1.hum1
- rust-main-1.96.1-1.hum1
- RHSA-2026:26989
- RHSA-2026:34975
Confirm against the vendor advisory before you patch.
- 2.2.2
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
- netavark-main-2.0.0-1.hum1
- rust-main-1.96.1-1.hum1
- RHSA-2026:26989
- RHSA-2026:34975
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
Mitigation checklist
- Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official advisory · high-confidence parse· fetched 11 days ago·verify at source
Get an email when Red Hat RHEL & SELinux publishes the next one.
See Red Hat RHEL & SELinux's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).
More Red Hat Linux advisories
- CVE-2026-111497Oct 22, 2026Out-of-Bounds Write in Google Brotli Decoder
- CVE-2026-48710May 26, 2026Security restriction bypass via malformed HTTP Host header
- CVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
- CVE-2026-109619Oct 21, 2026fatal error handling retains stale request state leading to use-after-free
- CVE-2026-109618Oct 21, 2026OOM bailout during request parsing leads to memory corruption and RCE
- CVE-2026-97229Oct 13, 2026integer overflow issue in CI/CD regular expression compiler
iPhone and Android apps · New on the App Store
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 34 official vendor sources and 160+ reviewed platform categories.
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.