{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-54225 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-54225 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54225 is a high-severity denial of service vulnerability in Apache Cxf, published on 6 Aug 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-54225 and fix it if it is affected.\n\nWhat it is: CVE-2026-54225 is a high-severity denial of service vulnerability in Apache Cxf, published on 6 Aug 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-54225 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-54225/ (Markdown: https://insights.sbomify.com/CVE-2026-54225/index.md)","id":"CVE-2026-54225","markdown":"https://insights.sbomify.com/CVE-2026-54225/index.md","name":"CVE-2026-54225","record":{"aliases":["GHSA-h9mr-9vh5-65gw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Java web services library","requires_auth":"none","summary":"Attackers can cause denial of service by sending large attachments if the default size limit is not explicitly configured 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":"Apache CXF allows to control the maximum attachment size via the \"attachment-max-size\". Prior to Apache CXF 4.2.3 and 4.1.8 and 3.6.12, there was no default placed on this size, meaning that a denial of service attack is possible if the user doesn't explicitly set the limit. Users should update to Apache CXF 4.2.3 or 4.1.8 or 3.6.12 which fixes this problem by imposing a default attachment size limit of 50mb.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apache CXF: Denial of Service attack via large attachments","id":"CVE-2026-54225","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 Kvrocks: RESTORE IntSet Integer Overflow Leads to Remote DoS","id":"CVE-2026-54226"},"packages":[],"prev":{"headline":"Denial of Service in UBB.threads","id":"CVE-2026-54224"},"products":["Apache CXF"],"published":"2026-08-06","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-08-07","vendors":["Apache Software Foundation"]},"summary":"Attackers can cause denial of service by sending large attachments if the default size limit is not explicitly configured in Apache CXF.","url":"https://insights.sbomify.com/CVE-2026-54225/"}