{"answers":{"affected":"3 open source packages ship an affected version, including peppol-py and peppol_py.","exploited":"There is no known exploitation of CVE-2025-66371 in the wild and no public exploit code.","fix":"Upgrade peppol-py to 1.1.1 or later.","what":"CVE-2025-66371 is a medium-severity vulnerability in Iteras Peppol-py, published on 28 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66371 and fix it if it is affected.\n\nWhat it is: CVE-2025-66371 is a medium-severity vulnerability in Iteras Peppol-py, published on 28 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-66371 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- peppol-py (PyPI): affected all versions; fixed in 1.1.1\n- peppol-py (PyPI): affected all versions; fixed in 1.1.1\n- peppol_py (PyPI): affected all versions; fixed in 1.1.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-2025-66371/ (Markdown: https://insights.sbomify.com/CVE-2025-66371/index.md)","id":"CVE-2025-66371","markdown":"https://insights.sbomify.com/CVE-2025-66371/index.md","name":"CVE-2025-66371","record":{"aliases":["GHSA-24hm-wm2h-h8w7","PYSEC-2026-1765"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Peppol XML library","requires_auth":"low_privilege","summary":"An attacker can exploit an XML External Entity vulnerability in Peppol-py to read local files and expose their content to a remote host.","user_interaction":"not_required","vuln_class":"xxe"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-611","name":"Improper Restriction of XML External Entity Reference"}],"description":"Peppol-py before 1.1.1 allows XXE attacks because of the Saxon configuration. When validating XML-based invoices, the XML parser could read files from the filesystem and expose their content to a remote host.","ecosystems":["PyPI"],"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":"Peppol-py is vulnerable to XXE attacks due to Saxon configuration","id":"CVE-2025-66371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xxe","year":"2025"},"n_packages":3,"n_references":4,"next":{"headline":"Mustangproject allows exfiltrating files via XXE attacks","id":"CVE-2025-66372"},"packages":[{"ecosystem":"PyPI","fixed":["1.1.1"],"introduced":["0"],"last_affected":[],"package":"peppol-py","purl":"pkg:pypi/peppol-py","source":"GHSA-24hm-wm2h-h8w7"},{"ecosystem":"PyPI","fixed":["1.1.1"],"introduced":["0"],"last_affected":[],"package":"peppol-py","purl":"pkg:pypi/peppol-py","source":"PYSEC-2026-1765"},{"ecosystem":"PyPI","fixed":["1.1.1"],"introduced":["0"],"last_affected":[],"package":"peppol_py","purl":null,"source":"GHSA-24hm-wm2h-h8w7"}],"prev":{"headline":"XML external entity in kivitendo","id":"CVE-2025-66370"},"products":["Peppol-py"],"published":"2025-11-28","related":[],"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":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-27","vendors":["Iteras"]},"summary":"An attacker can exploit an XML External Entity vulnerability in Peppol-py to read local files and expose their content to a remote host.","url":"https://insights.sbomify.com/CVE-2025-66371/"}