AI Science Tracker

Apache CXF: Apache CXF: The attachment header size and count limits can be bypassed, which allows denial of service through memory exhaustion.

Apache CXF · AI involvement attributed to This issue was found using Claude agents to study the security of open-source projects and independently by Mike Read (github.com/Michael-JRead)

Finding and attribution

In Apache CXF, the parser for multipart/MTOM attachment part headers did not fully enforce the configured attachment-max-header-size (default 300 characters) and attachment-headers-max-count (default 500) limits. The size limit was applied only to each physical line, not to a header value built from continuation lines or to the combined values of a repeated header. The count limit was checked against the number of distinct header names, not the total number of header lines. A remote, unauthentic

Product: Apache CXF. AI system: This issue was found using Claude agents to study the security of open-source projects and independently by Mike Read (github.com/Michael-JRead). Team / organization: apache (CNA); AI attribution as credited in the CVE record.

CVE identifiers: CVE-2026-107937.

AI and human contribution (source account): The CNA record credits 'This issue was found using Claude agents to study the security of open-source projects and independently by Mike Read (github.com/Michael-JRead)'. It states the AI attribution as written there and does not describe the model's operation, autonomy or the human validation steps; none is inferred.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The CNA record establishes a coordinated disclosure with the credit above. It does not establish exploitation in the wild or a zero-day incident.

Remediation status: not established. The CNA record states no fixed version, patch or solution; check the vendor advisory.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 9 Oct 2026. AI attribution date not established by the source. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 7.5. Documented technical effects: Not available.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

Technical effects, prerequisites and exploitation evidence are not established here. Missing evidence does not establish absence of exploitation.

Documented fix: The CNA record states no fixed version, patch or solution; check the vendor advisory.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases