{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82463 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82463 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82463 is a high-severity authentication bypass vulnerability in pac4j, published on 29 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82463 and fix it if it is affected.\n\nWhat it is: CVE-2026-82463 is a high-severity authentication bypass vulnerability in pac4j, published on 29 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-82463 in the wild and no public exploit code.\n\nAffected product: pac4j. 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-82463/ (Markdown: https://insights.sbomify.com/CVE-2026-82463/index.md)","id":"CVE-2026-82463","markdown":"https://insights.sbomify.com/CVE-2026-82463/index.md","name":"CVE-2026-82463","record":{"aliases":["GHSA-f66h-84rm-53q7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Java security library","requires_auth":"low_privilege","summary":"Attackers can bypass authorization checks in pac4j-core by exploiting reversed profile type validation logic to access restricted resources.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"pac4j-core before 6.5.6 contains an authentication bypass vulnerability in CheckProfileTypeAuthorizer that reverses the profile type validation logic. Attackers can authenticate through a weaker client and access resources requiring a stronger profile type by satisfying generic profile checks.","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":"pac4j-core before 6.5.6 Authorization Bypass via Reversed Profile Type Check","id":"CVE-2026-82463","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"pac4j-core before 6.5.6 Open Redirect via Backslash Logout","id":"CVE-2026-82464"},"packages":[],"prev":{"headline":"pac4j-oidc before 6.5.6 Authentication Bypass via Access Token Substitution","id":"CVE-2026-82462"},"products":["pac4j"],"published":"2026-08-29","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":"total"},"state":"PUBLISHED","updated":"2026-09-02","vendors":["pac4j"]},"summary":"Attackers can bypass authorization checks in pac4j-core by exploiting reversed profile type validation logic to access restricted resources.","url":"https://insights.sbomify.com/CVE-2026-82463/"}