Skip to main content
VulnerabilityPublished

CVE-2026-91865: Apache Neethi · Unthrottled Resource Allocation

Affects Apache NeethiSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High : upgrade to 3.2.4 soon.

Data as of 5 Nov 2026, 00:01 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade Apache to 3.2.4.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache NeethiAffected
  • <3.2.4
Fixed in
  • 3.2.4
MavenApache Software Foundation/org.apache.neethi:neethipkg:maven/Apache Software Foundation/org.apache.neethi:neethiOther threatsAffected
  • <3.2.4
Fixed in
  • 3.2.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users are advised to upgrade Apache Neethi to version 3.2.4 or later, where this vulnerability is fixed. No other mitigations are indicated.

Description

A small WS-Policy document using repeated policy references can force Neethi to re-expand the same references exponentially during normalization, consuming huge amounts of CPU and memory (denial of service). Users are recommended to upgrade to version 3.2.4, which fixes this issue.

References

Community reviews

Loading reviews…