CVE-2023-22463

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 70% (99th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Weaponized
9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 70%
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 70%CVSS: 9.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

KubePi is a k8s panel. The jwt authentication function of KubePi through version 1.6.2 uses hard-coded Jwtsigkeys, resulting in the same Jwtsigkeys for all online projects. This means that an attacker can forge any jwt token to take over the administrator account of any online project. Furthermore, they may use the administrator to take over the k8s cluster of the target enterprise. session.go, the use of hard-coded JwtSigKey, allows an attacker to use this value to forge jwt tokens arbitrarily. The JwtSigKey is confidential and should not be hard-coded in the code. The vulnerability has been fixed in 1.6.3. In the patch, JWT key is specified in app.yml. If the user leaves it blank, a random key will be used. There are no workarounds aside from upgrading.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
87
EG Risk 87/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation70% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
70%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
70% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-23). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

January 4, 2023

Last Modified

November 21, 2024

Advisory Details (4)

Auto-updated Oct 10, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

Hardcoded Jwtsigkeys allows malicious actor to login with a forged JWT token · Advisory · 1Panel-dev/KubePi · GitHub

https://github.com/KubeOperator/KubePi/security/advisories/GHSA-vjhf-8vqx-vqpq
GitHub release Patch Available

v1.6.3

Patch available: KubeOperator/KubePi v1.6.3

https://github.com/KubeOperator/KubePi/releases/tag/v1.6.3
GitHub commit Patch Available

commit 3be58b8df5bc (KubeOperator/KubePi)

Patch available: KubeOperator/KubePi v1.6.3 (contains commit 3be58b8df5bc)

https://github.com/KubeOperator/KubePi/commit/3be58b8df5bc05d2343c30371dd5fcf6a9fbbf8b
Web page

KubePi/internal/api/v1/session/session.go at da784f5532ea2495b92708cacb32703bff3a45a3 · 1Panel-dev/KubePi · GitHub

https://github.com/KubeOperator/KubePi/blob/da784f5532ea2495b92708cacb32703bff3a45a3/internal/api/v1/session/session.go#L35

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/KubeOperator/kubepi—
  • every version up to 1.6.3: fixed in 1.6.3
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 32× 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 90 of 126 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. 10 repeat rows among the latest 100 are merged into the row they repeat. The 36 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 20:43 UTCEG score recompute
  2. 2026-10-22 21:38 UTCEG score recompute
  3. 2026-10-22 16:30 UTCEPSS rescoreEPSS 70% · 99th percentile
  4. 2026-10-21 22:32 UTCEG score recompute
  5. 2026-10-21 16:29 UTCEPSS rescoreEPSS 70% · 99th percentile
  6. 2026-10-20 23:31 UTCEG score recompute
  7. 2026-10-20 16:29 UTCEPSS rescoreEPSS 70% · 99th percentile
  8. 2026-10-20 00:29 UTCEG score recompute
  9. 2026-10-18 23:21 UTCEG score recompute
  10. 2026-10-18 16:29 UTCEPSS rescoreEPSS 70% · 99th percentile
  11. 2026-10-18 08:13 UTCEG score recompute
  12. 2026-10-18 00:18 UTCEG score recompute
  13. 2026-10-17 01:14 UTCEG score recompute
  14. 2026-10-16 16:35 UTCEPSS rescoreEPSS 70% · 99th percentile
  15. 2026-10-16 01:21 UTCEG score recompute
  16. 2026-10-14 20:50 UTCEG score recompute
  17. 2026-10-14 16:29 UTCEPSS rescoreEPSS 70% · 99th percentile
  18. 2026-10-13 16:43 UTCEG score recompute
  19. 2026-10-13 16:29 UTCEPSS rescoreEPSS 70% · 99th percentile
  20. 2026-10-12 17:38 UTCEG score recompute
  21. 2026-10-12 16:30 UTCEPSS rescoreEPSS 70% · 99th percentile
  22. 2026-10-11 21:59 UTCEG score recompute
  23. 2026-10-10 19:57 UTCEPSS rescoreEPSS 70% · 99th percentile
  24. 2026-10-09 20:05 UTCEPSS rescoreEPSS 70% · 99th percentile
  25. 2026-10-07 23:45 UTCEPSS rescoreEPSS 70% · 99th percentile
Show 65 more
  1. 2026-10-05 17:40 UTCEPSS rescoreEPSS 70% · 99th percentile
  2. 2026-10-03 14:23 UTCEPSS rescoreEPSS 70% · 99th percentile
  3. 2026-10-01 19:47 UTCEPSS rescoreEPSS 70% · 99th percentile
  4. 2026-09-30 16:17 UTCEG score recompute
  5. 2026-09-26 15:55 UTCEPSS rescoreEPSS 70% · 99th percentile
  6. 2026-09-26 00:22 UTCEPSS rescoreEPSS 70% · 99th percentile
  7. 2026-09-24 14:01 UTCEPSS rescoreEPSS 70% · 99th percentile
  8. 2026-09-24 01:06 UTCOSV refresh
  9. 2026-09-23 13:45 UTCEPSS rescoreEPSS 70% · 99th percentile
  10. 2026-09-22 14:45 UTCEPSS rescoreEPSS 70% · 99th percentile
  11. 2026-09-19 15:38 UTCEPSS rescoreEPSS 70% · 99th percentile
  12. 2026-09-18 19:25 UTCEPSS rescoreEPSS 70% · 99th percentile
  13. 2026-09-17 19:24 UTCEPSS rescoreEPSS 70% · 99th percentile
  14. 2026-09-16 14:05 UTCEPSS rescoreEPSS 70% · 99th percentile
  15. 2026-09-16 05:11 UTCEPSS rescoreEPSS 70% · 99th percentile
  16. 2026-09-13 16:44 UTCEPSS rescoreEPSS 70% · 99th percentile
  17. 2026-09-12 14:58 UTCEPSS rescoreEPSS 70% · 99th percentile
  18. 2026-09-11 09:34 UTCEPSS rescoreEPSS 70% · 99th percentile
  19. 2026-09-06 13:45 UTCEPSS rescoreEPSS 70% · 99th percentile
  20. 2026-09-05 15:25 UTCEPSS rescoreEPSS 70% · 99th percentile
  21. 2026-09-04 19:24 UTCOSV refresh
  22. 2026-09-04 13:57 UTCEPSS rescoreEPSS 70% · 99th percentile
  23. 2026-09-04 05:04 UTCEPSS rescoreEPSS 70% · 99th percentile
  24. 2026-09-01 13:51 UTCEPSS rescoreEPSS 70% · 99th percentile
  25. 2026-08-30 19:15 UTCEPSS rescoreEPSS 70% · 99th percentile
  26. 2026-08-30 01:19 UTCEPSS rescoreEPSS 70% · 99th percentile
  27. 2026-08-28 21:38 UTCEPSS rescoreEPSS 70% · 99th percentile
  28. 2026-08-26 14:43 UTCEPSS rescoreEPSS 70% · 99th percentile
  29. 2026-08-24 14:14 UTCEPSS rescoreEPSS 70% · 99th percentile
  30. 2026-08-21 23:46 UTCEPSS rescoreEPSS 70% · 99th percentile
  31. 2026-08-20 22:53 UTCEPSS rescoreEPSS 70% · 99th percentile
  32. 2026-08-19 17:01 UTCEPSS rescoreEPSS 70% · 99th percentile
  33. 2026-08-18 06:34 UTCOSV refresh
  34. 2026-08-16 14:53 UTCEPSS rescoreEPSS 70% · 99th percentile
  35. 2026-08-16 02:12 UTCEPSS rescoreEPSS 70% · 99th percentile
  36. 2026-08-15 01:27 UTCEPSS rescoreEPSS 70% · 99th percentile
  37. 2026-08-13 21:58 UTCEPSS rescoreEPSS 70% · 99th percentile
  38. 2026-08-12 13:48 UTCEPSS rescoreEPSS 70% · 99th percentile
  39. 2026-08-07 16:24 UTCEPSS rescoreEPSS 70% · 99th percentile
  40. 2026-08-05 19:15 UTCEPSS rescoreEPSS 70% · 99th percentile
  41. 2026-08-03 01:57 UTCOSV refresh
  42. 2026-08-01 04:13 UTCEPSS rescoreEPSS 70% · 99th percentile
  43. 2026-07-30 16:26 UTCEPSS rescoreEPSS 70% · 99th percentile
  44. 2026-07-30 01:28 UTCEPSS rescoreEPSS 70% · 99th percentile
  45. 2026-07-28 15:34 UTCEPSS rescoreEPSS 70% · 99th percentile
  46. 2026-07-26 14:52 UTCEPSS rescoreEPSS 70% · 99th percentile
  47. 2026-07-24 14:15 UTCEPSS rescoreEPSS 70% · 99th percentile
  48. 2026-07-23 14:16 UTCEPSS rescoreEPSS 70% · 99th percentile
  49. 2026-07-23 02:18 UTCEG score recompute
  50. 2026-07-22 23:06 UTCEG score recompute
  51. 2026-07-22 14:06 UTCEPSS rescoreEPSS 70% · 99th percentile
  52. 2026-07-20 17:05 UTCEPSS rescoreEPSS 70% · 99th percentile
  53. 2026-07-16 17:01 UTCEPSS rescoreEPSS 70% · 99th percentile
  54. 2026-07-16 10:53 UTCOSV refresh
  55. 2026-07-15 16:56 UTCEPSS rescoreEPSS 70% · 99th percentile
  56. 2026-07-13 22:28 UTCEPSS rescoreEPSS 70% · 99th percentile
  57. 2026-07-12 05:45 UTCEPSS rescoreEPSS 70% · 99th percentile
  58. 2026-07-09 19:08 UTCEPSS rescoreEPSS 70% · 99th percentile
  59. 2026-07-07 13:44 UTCEPSS rescoreEPSS 70% · 99th percentile
  60. 2026-07-04 06:29 UTCEPSS rescoreEPSS 70% · 99th percentile
  61. 2026-07-02 16:58 UTCEPSS rescoreEPSS 70% · 99th percentile
  62. 2026-07-01 15:04 UTCEPSS rescoreEPSS 70% · 99th percentile
  63. 2026-06-29 14:04 UTCEPSS rescoreEPSS 70% · 99th percentile
  64. 2026-06-28 14:06 UTCEPSS rescoreEPSS 70% · 99th percentile
  65. 2026-06-28 09:49 UTCOSV refresh

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2023/CVE-2023-22463.yaml
    Published Sep 15, 2023

    KubePi JwtSigKey - Admin Authentication Bypass

    Open source ↗

Frequently asked(5)

What is CVE-2023-22463?
CVE-2023-22463 is a critical-severity vulnerability; its CVE record was published on January 4, 2023. KubePi is a k8s panel. The jwt authentication function of KubePi through version 1.6.2 uses hard-coded Jwtsigkeys, resulting in the same Jwtsigkeys for all online projects. This means that an attacker can forge any jwt token to take over the administrator account of any online project. Furthermore,…
When was the CVE record for CVE-2023-22463 published?
The CVE record for CVE-2023-22463 was published on January 4, 2023. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 21, 2024; the record at its source may have been updated since.
Is CVE-2023-22463 actively exploited?
CVE-2023-22463 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: CISA's SSVC data says a public PoC exists and its EPSS is 50% or more. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 70% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-22463?
CVE-2023-22463 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-22463?
A fix for CVE-2023-22463 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-22463

Explore →

Is Your Infrastructure Affected by CVE-2023-22463?

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