CVE-2026-82463

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-29. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 8.1Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
The EG Score, 8.1 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.6%
EPSS %ILE
44th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 29, 2026

Last Modified

September 2, 2026

Advisory Details (5)

Auto-updated Aug 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
Web page

pac4j-core before 6.5.6 Authorization Bypass via Reversed Profile Type Check | Advisories | VulnCheck

https://www.vulncheck.com/advisories/pac4j-core-before-6.5.6-authorization-bypass-via-reversed-profile-type-check
Web page

GitHub - pac4j/pac4j: Security engine for Java (authentication, authorization, multi frameworks): OpenID Connect, SAML2, CAS, OAuth, LDAP, JWT... · GitHub

https://github.com/pac4j/pac4j
Web page

pac4j/pac4j-core/src/main/java/org/pac4j/core/authorization/authorizer/CheckProfileTypeAuthorizer.java at pac4j-parent-6.5.5 · pac4j/pac4j · GitHub

https://github.com/pac4j/pac4j/blob/pac4j-parent-6.5.5/pac4j-core/src/main/java/org/pac4j/core/authorization/authorizer/CheckProfileTypeAuthorizer.java
Web page

Security advisory for pac4j-core, pac4j-oidc and pac4j-saml | pac4j

https://www.pac4j.org/blog/security-advisory-pac4j-core-oidc-saml.html
GitHub commit

commit 2270c3ff70e9 (pac4j/pac4j)

Fix landed in pac4j/pac4j commit 2270c3ff70e9 — awaiting tagged release

https://github.com/pac4j/pac4j/commit/2270c3ff70e93cc43831e75702acd5135531237e

Vendor Advisories for CVE-2026-82463(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 107× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 172 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 72 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  2. 2026-10-13 06:03 UTCEG score recompute
  3. 2026-10-13 06:03 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  5. 2026-10-12 14:55 UTCEG score recompute
  6. 2026-10-11 19:19 UTCEG score recompute
  7. 2026-10-11 16:36 UTCEG score recompute
  8. 2026-10-11 13:54 UTCEG score recompute
  9. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  10. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  11. 2026-10-10 12:40 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-10 00:45 UTCEG score recompute
  13. 2026-10-10 00:45 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  15. 2026-10-09 02:34 UTCEG score recompute
  16. 2026-10-09 02:34 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  18. 2026-10-08 00:45 UTCEG score recompute
  19. 2026-10-08 00:45 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  21. 2026-10-07 01:33 UTCEG score recompute
  22. 2026-10-07 01:33 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  23. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  24. 2026-10-06 13:37 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-10-06 01:43 UTCEG score recompute
Show 75 more
  1. 2026-10-06 01:43 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  2. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  3. 2026-10-05 13:48 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-10-05 01:42 UTCEG score recompute
  5. 2026-10-05 01:42 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  7. 2026-10-04 13:48 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  8. 2026-10-04 01:53 UTCEG score recompute
  9. 2026-10-04 01:53 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  10. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  11. 2026-10-03 13:36 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  12. 2026-10-02 19:48 UTCEG score recompute
  13. 2026-10-02 19:48 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  14. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  15. 2026-10-02 07:54 UTCEG score recompute
  16. 2026-10-02 07:54 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  17. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 44th percentile
  18. 2026-10-01 19:47 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  19. 2026-10-01 07:42 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  20. 2026-09-30 19:48 UTCEG score recompute
  21. 2026-09-30 19:48 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  23. 2026-09-30 03:48 UTCEG score recompute
  24. 2026-09-30 03:48 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  25. 2026-09-29 09:51 UTCEG score recompute
  26. 2026-09-29 09:51 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  27. 2026-09-28 21:07 UTCEG score recompute
  28. 2026-09-28 21:07 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  29. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  30. 2026-09-28 08:06 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  31. 2026-09-27 20:10 UTCEG score recompute
  32. 2026-09-27 20:10 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  33. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  34. 2026-09-27 08:16 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  35. 2026-09-26 20:22 UTCEG score recompute
  36. 2026-09-26 20:22 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  38. 2026-09-26 08:01 UTCEG score recompute
  39. 2026-09-26 08:01 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  40. 2026-09-25 11:28 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  41. 2026-09-24 23:24 UTCEG score recompute
  42. 2026-09-24 23:24 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  43. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.6% · 43rd percentile
  44. 2026-09-24 11:21 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  45. 2026-09-23 23:27 UTCEG score recompute
  46. 2026-09-23 23:27 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  47. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-09-23 11:33 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  49. 2026-09-22 23:39 UTCEG score recompute
  50. 2026-09-22 23:39 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  51. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  52. 2026-09-22 11:33 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  53. 2026-09-21 23:39 UTCEG score recompute
  54. 2026-09-21 23:39 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  55. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  56. 2026-09-21 11:45 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  57. 2026-09-20 23:51 UTCEG score recompute
  58. 2026-09-20 23:51 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  59. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  60. 2026-09-20 11:56 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  61. 2026-09-19 23:37 UTCEG score recompute
  62. 2026-09-19 23:37 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  63. 2026-09-19 11:43 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  64. 2026-09-18 23:48 UTCEG score recompute
  65. 2026-09-18 23:48 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  66. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  67. 2026-09-18 11:54 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  68. 2026-09-18 00:00 UTCEG score recompute
  69. 2026-09-18 00:00 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  70. 2026-09-17 11:16 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  71. 2026-09-16 23:22 UTCEG score recompute
  72. 2026-09-16 23:22 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1
  73. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  74. 2026-09-16 11:28 UTCEG score recompute
  75. 2026-09-16 11:27 UTCGHSA enrichmentGHSA-f66h-84rm-53q7 · GitHub severity HIGH · GitHub CVSS 8.1

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82463?
CVE-2026-82463 is a high-severity vulnerability; its CVE record was published on August 29, 2026. 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.
When was CVE-2026-82463 made public?
CVE-2026-82463 was made public on August 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on August 29, 2026. EchelonGraph's copy of the record carries a last-modified date of September 2, 2026; the record at its source may have been updated since.
Is CVE-2026-82463 actively exploited?
CVE-2026-82463 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82463?
CVE-2026-82463 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82463?
An upstream fix for CVE-2026-82463 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-82463 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-82463

Explore →

Is Your Infrastructure Affected by CVE-2026-82463?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs