CVE-2026-91866

7.5

Apache · Neethi

Apache Neethi is vulnerable to a denial of service attack where crafted WS-Policy documents trigger exponential CPU consumption during policy intersection.

Executive summary

A vulnerability in Apache Neethi allows unauthenticated attackers to cause a denial of service by exhausting CPU resources through malicious WS-Policy document submissions.

Vulnerability

This is a denial of service vulnerability involving the policy-intersection function. An unauthenticated attacker can supply specially crafted WS-Policy documents to force the application to perform exponential amounts of computational work.

Business impact

The successful exploitation of this vulnerability results in a denial of service, which can render critical applications relying on Apache Neethi unavailable to legitimate users. With a CVSS score of 7.5, this high-severity flaw poses a significant operational risk, as the service exhaustion can lead to business disruption and potential loss of productivity for organizations dependent on affected web services.

Remediation

Immediate Action: Upgrade the Apache Neethi library to version 3.2.4 or later to apply the necessary performance constraints on policy-intersection calculations.

Proactive Monitoring: Monitor server CPU utilization metrics for sudden, sustained spikes that correlate with incoming web traffic or specific policy-related service calls.

Compensating Controls: Implement rate limiting or request size restrictions at the Web Application Firewall (WAF) or API gateway level to filter out malicious or overly complex WS-Policy payloads before they reach the backend service.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

Given the high severity of this vulnerability and the ease with which an unauthenticated attacker can trigger the CPU exhaustion state, immediate patching is advised. Organizations should prioritize updating their dependencies to Apache Neethi 3.2.4 to eliminate the underlying logic flaw and restore service stability.

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.