{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.tika:tika-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11796 in the wild and no public exploit code.","fix":"Upgrade org.apache.tika:tika-core to 1.19.1 or later.","what":"CVE-2018-11796 is a high-severity vulnerability in Apache Tika, published on 9 Oct 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11796 and fix it if it is affected.\n\nWhat it is: CVE-2018-11796 is a high-severity vulnerability in Apache Tika, published on 9 Oct 2018. 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-2018-11796 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.tika:tika-core (Maven): affected from 0.1; fixed in 1.19.1\n- org.apache.tika:tika-core (Maven): affected from 0.1; fixed in 1.19.1\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-2018-11796/ (Markdown: https://insights.sbomify.com/CVE-2018-11796/index.md)","id":"CVE-2018-11796","markdown":"https://insights.sbomify.com/CVE-2018-11796/index.md","name":"CVE-2018-11796","record":{"aliases":["GHSA-h8q5-g2cj-qr5h","UBUNTU-CVE-2018-11796"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Tika library","requires_auth":"none","summary":"Attackers can cause denial of service via XML entity expansion in Apache Tika due to improper parser reset handling.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"tika","vendor":"apache"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"In Apache Tika 1.19 (CVE-2018-11761), we added an entity expansion limit for XML parsing. However, Tika reuses SAXParsers and calls reset() after each parse, which, for Xerces2 parsers, as per the documentation, removes the user-specified SecurityManager and thus removes entity expansion limits after the first parse. Apache Tika versions from 0.1 to 1.19 are therefore still vulnerable to entity expansions which can lead to a denial of service attack. Users should upgrade to 1.19.1 or later.","ecosystems":["Maven"],"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":"Apache Tika is vulnerable to entity expansions which can lead to a denial of service attack","id":"CVE-2018-11796","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xxe","year":"2018"},"n_packages":2,"n_references":4,"next":{"headline":"In Apache PDFBox a carefully crafted PDF file can trigger an extremely long running computation","id":"CVE-2018-11797"},"packages":[{"ecosystem":"Maven","fixed":["1.19.1"],"introduced":["0.1"],"last_affected":[],"package":"org.apache.tika:tika-core","purl":null,"source":"GHSA-h8q5-g2cj-qr5h"},{"ecosystem":"Maven","fixed":["1.19.1"],"introduced":["0.1"],"last_affected":[],"package":"org.apache.tika:tika-core","purl":"pkg:maven/org.apache.tika/tika-core","source":"GHSA-h8q5-g2cj-qr5h"}],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-11795"},"products":["Apache Tika"],"published":"2018-10-09","related":[{"cvss_score":8.8,"headline":"Allocation of Resources Without Limits or Throttling in Apache Tika","id":"CVE-2019-10088","kev_date_added":null,"published":"2019-08-02"},{"cvss_score":8.4,"headline":"Apache Tika has XXE vulnerability","id":"CVE-2025-66516","kev_date_added":null,"published":"2025-12-04"},{"cvss_score":8.4,"headline":"Apache Tika PDF parser module: XXE vulnerability in PDFParser's handling of XFA","id":"CVE-2025-54988","kev_date_added":null,"published":"2025-08-20"},{"cvss_score":8.1,"headline":"Command injection in org.apache.tika:tika-core","id":"CVE-2018-1335","kev_date_added":null,"published":"2018-04-25"},{"cvss_score":7.8,"headline":"Allocation of Resources Without Limits or Throttling in Apache Tika","id":"CVE-2019-10094","kev_date_added":null,"published":"2019-08-02"},{"cvss_score":7.8,"headline":"Apache Tika does not properly initialize the XML parser or choose handlers","id":"CVE-2016-4434","kev_date_added":null,"published":"2017-09-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Apache Software Foundation"]},"summary":"Attackers can cause denial of service via XML entity expansion in Apache Tika due to improper parser reset handling.","url":"https://insights.sbomify.com/CVE-2018-11796/"}