{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56447 exists.","fix":"No fix has been published for CVE-2025-56447 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-56447 is a critical authentication bypass vulnerability in n/a, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-56447 and fix it if it is affected.\n\nWhat it is: CVE-2025-56447 is a critical authentication bypass vulnerability in n/a, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56447 exists.\n\nAffected product: n/a. 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-56447/ (Markdown: https://insights.sbomify.com/CVE-2025-56447/index.md)","id":"CVE-2025-56447","markdown":"https://insights.sbomify.com/CVE-2025-56447/index.md","name":"CVE-2025-56447","record":{"aliases":["GHSA-4p8g-cpw8-6wfm"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["security_bypass","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"TM2 Monitoring","requires_auth":"none","summary":"Attackers can bypass authentication and access plaintext credentials in TM2 Monitoring, leading to unauthorized access and data exposure.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"TM2 Monitoring v3.04 contains an authentication bypass and plaintext credential disclosure.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2025-56447","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2025-56448"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2025-56438"},"products":["n/a"],"published":"2025-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can bypass authentication and access plaintext credentials in TM2 Monitoring, leading to unauthorized access and data exposure.","url":"https://insights.sbomify.com/CVE-2025-56447/"}