CVE-2026-91864

7.5

Apache · Apache Neethi

A heap exhaustion vulnerability in Apache Neethi allows unauthenticated remote attackers to cause a denial of service by sending specially crafted WS-Policy documents.

Executive summary

Apache Neethi is vulnerable to a heap exhaustion denial of service attack caused by improper handling of policy assertions in WS-Policy documents.

Vulnerability

This is a memory exhaustion flaw where the library fails to enforce size limits on content within WS-Policy assertions. An unauthenticated remote attacker can trigger this condition by providing a malicious document, resulting in a denial of service.

Business impact

The exploitation of this vulnerability leads to an application denial of service, which can cause significant operational disruption for systems relying on Apache Neethi for policy processing. With a CVSS score of 7.5, the risk is classified as High due to the ease of exploitation over the network without requiring authentication. Unchecked heap consumption may result in service crashes, requiring manual intervention to restore availability.

Remediation

Immediate Action: Upgrade Apache Neethi to version 3.2.4 or later to implement the necessary size limit checks on policy assertions.

Proactive Monitoring: Monitor application server logs and system heap usage metrics for unusual spikes or sudden process terminations that could indicate a memory exhaustion attempt.

Compensating Controls: Deploy a Web Application Firewall (WAF) or an XML gateway configured to inspect and validate the size of incoming WS-Policy documents before they reach the application layer.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the High severity rating and the potential for a complete service outage, organizations should prioritize patching Apache Neethi to version 3.2.4. Administrators must verify their dependency trees to ensure all instances of the library are updated, as this component is often bundled within larger middleware or integration frameworks.

More Apache CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by This issue was found using Claude agents to study the security of open-source projects, per the CVE Program record.