{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-107937 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-107937 is a high-severity denial of service vulnerability in Apache Cxf, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-107937 and fix it if it is affected.\n\nWhat it is: CVE-2026-107937 is a high-severity denial of service vulnerability in Apache Cxf, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-107937 in the wild and no public exploit code.\n\nAffected product: Apache Cxf. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-107937/ (Markdown: https://insights.sbomify.com/CVE-2026-107937/index.md)","id":"CVE-2026-107937","markdown":"https://insights.sbomify.com/CVE-2026-107937/index.md","name":"CVE-2026-107937","record":{"aliases":["CLEANSTART-2026-RF61847","GHSA-7cpr-66jm-x98h"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Java web services library","requires_auth":"none","summary":"Remote attackers can cause denial of service via memory exhaustion by bypassing attachment header limits in Apache CXF.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"cxf","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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, unauthenticated attacker could send a multipart request with very large folded or repeated part headers. The server would then allocate memory without bound, causing a denial of service. \nUsers are recommended to upgrade to versions 4.2.4 or 4.1.9 or 3.6.13, which fix this issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Denial of service in Apache CXF","id":"CVE-2026-107937","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"apache:cxf","products":["apache:cxf"],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache CXF: The Netty HTTP client transport does not perform TLS hostname verification.","id":"CVE-2026-107938"},"packages":[],"prev":{"headline":"Gvisor-tap-vsock: gvisor-tap-vsock: unathenticated arbitrary file deletion on the host via /expose","id":"CVE-2026-107935"},"products":["Apache CXF"],"published":"2026-10-09","related":[{"cvss_score":10,"headline":"XML Signature/Encryption Not Validated in Apache CXF","id":"CVE-2012-2379","kev_date_added":null,"published":"2013-01-03"},{"cvss_score":9.8,"headline":"Apache CXF: Unsafe deserialization of inbound JMS ObjectMessage","id":"CVE-2026-66909","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":9.8,"headline":"Apache CXF: DefaultEncryptingCodeDataProvider allows unlimited authorization code replay","id":"CVE-2026-68079","kev_date_added":null,"published":"2026-08-06"},{"cvss_score":9.8,"headline":"Apache CXF: OAuth2: Inverted IP Binding Check Defeats Security Control","id":"CVE-2026-50628","kev_date_added":null,"published":"2026-06-12"},{"cvss_score":9.8,"headline":"Apache CXF: Untrusted JMS configuration can lead to RCE","id":"CVE-2025-48913","kev_date_added":null,"published":"2025-08-08"},{"cvss_score":9.8,"headline":"Apache CXF SSRF Vulnerability","id":"CVE-2022-46364","kev_date_added":null,"published":"2022-12-13"},{"cvss_score":9.8,"headline":"Potential session hijack in Apache CXF","id":"CVE-2019-12419","kev_date_added":null,"published":"2019-11-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-15","vendors":["Apache Software Foundation"]},"summary":"Remote attackers can cause denial of service via memory exhaustion by bypassing attachment header limits in Apache CXF.","url":"https://insights.sbomify.com/CVE-2026-107937/"}