Medium [CVE-2026-89045] Denial of Service via negative length parameter
This medium-severity Red Hat Linux advisory covers CVE-2026-89045 affecting Exploit Intelligence, OpenShift Developer Tools and Services, Red Hat build of Apache Camel 4 for Quarkus 3.
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.
Summary
A flaw was found in zstd-jni. This vulnerability allows an attacker to trigger an infinite loop by providing negative length parameters to the ZstdInputStreamNoFinalizer.read() method.
This can cause the read method to spin indefinitely, holding the stream monitor and blocking other threads from accessing the stream, ultimately leading to a Denial of Service (DoS) for the affected application.
Red Hat rates this Moderate, consistent with upstream's own CVSS 3.1 score of 4.0, for the same reason: the negative length has to come from the calling application's own logic, not from an attacker-controlled value received directly over a wire protocol.
Where it is reachable, the failure is a single thread spinning and holding one stream instance's lock indefinitely, not memory corruption, data exposure, or privilege escalation, and it doesn't propagate to stream instances the hung caller isn't sharing.
That combination, a caller-side prerequisite plus an impact bounded to one thread and one stream object, is why this stays Moderate rather than Important despite being a straightforward-looking DoS trigger on paper. Weakness: CWE-835.
Affected products named by the advisory: Exploit Intelligence; OpenShift Developer Tools and Services; Red Hat build of Apache Camel 4 for Quarkus 3; Red Hat build of Apache Camel for Spring Boot 4; and 11 more.
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 2 hours ago·verify at source
- 1.5.7-14
Official advisory · high-confidence parse· fetched 2 hours ago·verify at source
Mitigation checklist
- If your integration calls read(byte[], int, int) directly with a computed length, for example a remaining-bytes calculation, add a len >= 0 check before the call. If you can't change the call site, avoid sharing a single ZstdInputStreamNoFinalizer instance across threads or requests, so a bad input only stalls the one caller that triggered it instead of every other caller waiting on the same stream.
Official advisory · high-confidence parse· fetched 2 hours 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.