{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-51677 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-51677 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-51677 is a critical vulnerability in n/a, published on 17 Jul 2026. 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-51677 and fix it if it is affected.\n\nWhat it is: CVE-2025-51677 is a critical vulnerability in n/a, published on 17 Jul 2026. 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-2025-51677 in the wild and no public exploit code.\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-51677/ (Markdown: https://insights.sbomify.com/CVE-2025-51677/index.md)","id":"CVE-2025-51677","markdown":"https://insights.sbomify.com/CVE-2025-51677/index.md","name":"CVE-2025-51677","record":{"aliases":["GHSA-27g6-g49f-v47g"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"openRISC OR1200 CPU","requires_auth":"none","summary":"An output mismatch between RTL and netlist in the openRISC OR1200 CPU can cause unexpected behavior, affecting hardware designers and integrators.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"An issue was discovered in openRISC OR1200 commit 83ac6b. An output mismatch between the RTL and the netlist of the or1200 cpu output port can lead to unexpected behavior.","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":"Other in n/a","id":"CVE-2025-51677","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Other in n/a","id":"CVE-2025-51678"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2025-51675"},"products":["n/a"],"published":"2026-07-17","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-20","vendors":["n/a"]},"summary":"An output mismatch between RTL and netlist in the openRISC OR1200 CPU can cause unexpected behavior, affecting hardware designers and integrators.","url":"https://insights.sbomify.com/CVE-2025-51677/"}