{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-45767 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-45767 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-45767 is a high-severity vulnerability in n/a, published on 1 Aug 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-45767 and fix it if it is affected.\n\nWhat it is: CVE-2025-45767 is a high-severity vulnerability in n/a, published on 1 Aug 2025. 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-45767 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-45767/ (Markdown: https://insights.sbomify.com/CVE-2025-45767/index.md)","id":"CVE-2025-45767","markdown":"https://insights.sbomify.com/CVE-2025-45767/index.md","name":"CVE-2025-45767","record":{"aliases":["DEBIAN-CVE-2025-45767","GHSA-m523-xm42-q7ff","UBUNTU-CVE-2025-45767"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript JOSE library","requires_auth":"none","summary":"The jose library uses weak encryption algorithms, potentially allowing attackers to bypass security controls, though the severity is disputed.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"jose v6.0.10 was discovered to contain weak encryption. NOTE: this is disputed by a third party because the claim of \"do not meet recommended security standards\" does not reflect guidance in a final publication.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Weak cryptography in n/a","id":"CVE-2025-45767","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2025-45768"},"packages":[],"prev":{"headline":"Weak cryptography in n/a","id":"CVE-2025-45766"},"products":["n/a"],"published":"2025-08-01","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-08-21","vendors":["n/a"]},"summary":"The jose library uses weak encryption algorithms, potentially allowing attackers to bypass security controls, though the severity is disputed.","url":"https://insights.sbomify.com/CVE-2025-45767/"}