{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27607 exists.","fix":"No fix has been published for CVE-2025-27607 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27607 is a high-severity vulnerability in nhairs python-json-logger, published on 7 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-27607 and fix it if it is affected.\n\nWhat it is: CVE-2025-27607 is a high-severity vulnerability in nhairs python-json-logger, published on 7 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27607 exists.\n\nAffected product: nhairs python-json-logger. 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-2025-27607/ (Markdown: https://insights.sbomify.com/CVE-2025-27607/index.md)","id":"CVE-2025-27607","markdown":"https://insights.sbomify.com/CVE-2025-27607/index.md","name":"CVE-2025-27607","record":{"aliases":["GHSA-wmxh-pxcx-9w24","UBUNTU-CVE-2025-27607"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Python logging library","requires_auth":"none","summary":"Attackers could execute code on systems installing development dependencies for Python JSON Logger due to a hijacked package name.","user_interaction":"required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"python_json_logger","vendor":"nhairs"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"Python JSON Logger is a JSON Formatter for Python Logging. Between 30 December 2024 and 4 March 2025 Python JSON Logger was vulnerable to RCE through a missing dependency. This occurred because msgspec-python313-pre was deleted by the owner leaving the name open to being claimed by a third party. If the package was claimed, it would allow them RCE on any Python JSON Logger user who installed the development dependencies on Python 3.13 (e.g. pip install python-json-logger[dev]). This issue has been resolved with 3.3.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-03-14","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-03-14T11:41:48Z","kind":"github_poc","ref":"https://github.com/Barsug/msgspec-python313-pre","stars":0,"title":"CVE-2025-27607 fix"}],"tier":"weaponised"},"has_fix":false,"headline":"Python JSON Logger has a Potential RCE via missing `msgspec-python313-pre` dependency","id":"CVE-2025-27607","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Self Cross-Site Scripting in Arduino IDE","id":"CVE-2025-27608"},"packages":[],"prev":{"headline":"Element Android PIN autologout bypass","id":"CVE-2025-27606"},"products":["python-json-logger"],"published":"2025-03-07","related":[],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-07","vendors":["nhairs"]},"summary":"Attackers could execute code on systems installing development dependencies for Python JSON Logger due to a hijacked package name.","url":"https://insights.sbomify.com/CVE-2025-27607/"}