{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-27371 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27371 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27371 is a medium-severity vulnerability in IETF RFC 7523, published on 3 Mar 2025."},"fix_prompt":"Check this codebase for CVE-2025-27371 and fix it if it is affected.\n\nWhat it is: CVE-2025-27371 is a medium-severity vulnerability in IETF RFC 7523, published on 3 Mar 2025. \nExploitation: There is no known exploitation of CVE-2025-27371 in the wild and no public exploit code.\n\nAffected product: IETF RFC 7523. 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-27371/ (Markdown: https://insights.sbomify.com/CVE-2025-27371/index.md)","id":"CVE-2025-27371","markdown":"https://insights.sbomify.com/CVE-2025-27371/index.md","name":"CVE-2025-27371","record":{"aliases":["GHSA-rh3q-7g79-rp3x"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-305","name":"Authentication Bypass by Primary Weakness"}],"description":"In certain IETF OAuth 2.0-related specifications, when the JSON Web Token Profile for OAuth 2.0 Client Authentication mechanism is used, there are ambiguities in the audience values of JWTs sent to authorization servers. The affected RFCs may include RFC 7523, and also RFC 7521, RFC 7522, RFC 9101 (JAR), and RFC 9126 (PAR).","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":"In certain IETF OAuth 2.0-related specifications, when the JSON Web Token Profile for OAuth 2.0 Client Authentication mechanism is used, the","id":"CVE-2025-27371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-27374"},"packages":[],"prev":{"headline":"Auth bypass in OpenID Connect","id":"CVE-2025-27370"},"products":["RFC 7523"],"published":"2025-03-03","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-04-25","vendors":["IETF"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-27371/"}