{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-52983 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-52983 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-52983 is a high-severity authentication bypass vulnerability in Juniper Junos, published on 11 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-52983 and fix it if it is affected.\n\nWhat it is: CVE-2025-52983 is a high-severity authentication bypass vulnerability in Juniper Junos, published on 11 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-52983 in the wild and no public exploit code.\n\nAffected product: Juniper Junos. 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-52983/ (Markdown: https://insights.sbomify.com/CVE-2025-52983/index.md)","id":"CVE-2025-52983","markdown":"https://insights.sbomify.com/CVE-2025-52983/index.md","name":"CVE-2025-52983","record":{"aliases":["GHSA-9cv5-8rg2-7cch"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Junos OS","requires_auth":"high_privilege","summary":"Attackers with private keys can log in as root on Junos OS VM Hosts even after public key removal, bypassing authentication controls.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"junos","vendor":"juniper"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/R:U/RE:M","version":"4.0"},"cwes":[{"id":"CWE-446","name":"UI Discrepancy for Security Feature"}],"description":"A UI Discrepancy for Security Feature\n\nvulnerability in the UI of Juniper Networks Junos OS on VM Host systems allows a network-based, unauthenticated attacker to access the device.\n\nOn VM Host Routing Engines (RE), even if the configured public key for root has been removed, remote users which are in possession of the corresponding private key can still log in as root.\nThis issue affects Junos OS:\n\n  *  all versions before 22.2R3-S7,\n  *  22.4 versions before 22.4R3-S5,\n  *  23.2 versions before 23.2R2-S3,\n  *  23.4 versions before 23.4R2-S3,\n  *  24.2 versions before 24.2R1-S2, 24.2R2.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Junos OS: After removing ssh public key authentication root can still log in","id":"CVE-2025-52983","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos","products":["juniper:junos"],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in Junos OS","id":"CVE-2025-52984"},"packages":[],"prev":{"headline":"Junos OS: MX Series: When specific SIP packets are processed the MS-MPC will crash","id":"CVE-2025-52982"},"products":["Junos OS"],"published":"2025-07-11","related":[{"cvss_score":9.8,"headline":"Juniper Junos OS EX Series and SRX Series PHP External Variable Modification","id":"CVE-2023-36845","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":8.8,"headline":"Juniper Junos OS Path Traversal","id":"CVE-2020-1631","kev_date_added":"2022-03-25","published":"2020-05-04"},{"cvss_score":6.7,"headline":"Juniper Junos OS Improper Isolation or Compartmentalization","id":"CVE-2025-21590","kev_date_added":"2025-03-13","published":"2025-03-12"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36851","kev_date_added":"2023-11-13","published":"2023-09-26"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series PHP External Variable Modification","id":"CVE-2023-36844","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36846","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series Missing Authentication for Critical Function","id":"CVE-2023-36847","kev_date_added":"2023-11-13","published":"2023-08-17"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Juniper Networks"]},"summary":"Attackers with private keys can log in as root on Junos OS VM Hosts even after public key removal, bypassing authentication controls.","url":"https://insights.sbomify.com/CVE-2025-52983/"}