{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-54431 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-54431 is a medium-severity vulnerability in OpenIDC liboauth2, published on 2 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54431 and fix it if it is affected.\n\nWhat it is: CVE-2026-54431 is a medium-severity vulnerability in OpenIDC liboauth2, published on 2 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-54431 in the wild and no public exploit code.\n\nAffected product: OpenIDC liboauth2. 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-2026-54431/ (Markdown: https://insights.sbomify.com/CVE-2026-54431/index.md)","id":"CVE-2026-54431","markdown":"https://insights.sbomify.com/CVE-2026-54431/index.md","name":"CVE-2026-54431","record":{"aliases":["AZL-91682","DEBIAN-CVE-2026-54431","GHSA-3pf6-g4x4-jm46","UBUNTU-CVE-2026-54431"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OAuth2 library","requires_auth":"none","summary":"Attackers can bypass DPoP proof validation by embedding private keys in the JWK header, allowing unauthorized token usage.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-358","name":"Improperly Implemented Security Check for Standard"}],"description":"In liboauth2 the Demonstrating Proof-of-Possession (DPoP) verifier accepts a proof whose JSON Web Key (jwk) header contains private key material. RFC 9449 section 4.3 step 7 requires the verifier to reject such a proof but oauth2_token_verify() function returns success for a malformed DPoP proof that embeds the private Elliptic Curve (EC) key in the header.\n\nThis issue was fixed in version 2.3.0","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Data Validation in liboauth2","id":"CVE-2026-54431","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in Webmail","id":"CVE-2026-54432"},"packages":[],"prev":{"headline":"Server-Site Request Forgery in liboauth2","id":"CVE-2026-54430"},"products":["liboauth2"],"published":"2026-07-02","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":"2026-07-02","vendors":["OpenIDC"]},"summary":"Attackers can bypass DPoP proof validation by embedding private keys in the JWK header, allowing unauthorized token usage.","url":"https://insights.sbomify.com/CVE-2026-54431/"}