CVE-2026-68453

HIGHPre-NVD 7.17.1
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

In the Linux kernel, the following vulnerability has been resolved:

s390/zcrypt: Fix buffer over-read in cca_cipher2protkey

Add validation of both the actual key buffer size and token length fields in all the cca_check_sec*token() functions. Additionally check in cca_gencipherkey() for possible underflow with returned key size.

The CCA token structures contain user-controlled len fields that were used in operations without proper validation against both the actual buffer size and minimum token structure size. An attacker could set this field larger than the actual buffer size, leading to reading beyond buffer boundaries. This may result in a kernel crash or exposure of memory via sending this as part of a request down to the crypto card. Also an attacker could have used a very small len value and thus enforce a buffer under-run which may produce similar effects as a over-read.

So now a key must

  • key buf length must be at least sizeof the token struct
  • the key len field inside the token must fit into the range of
sizeof key token struct ... key buf length

CVSS v3
7.1
EG Score
7.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 17, 2026

Advisory Details (3)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

s390/zcrypt: Fix buffer over-read in cca_cipher2protkey - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a57fd7fcdb63e2d5ceac78bbe825ec986062a9da
generic

s390/zcrypt: Fix buffer over-read in cca_cipher2protkey - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3b2abee2a678607ae27975bc6833785c2002df43
generic

s390/zcrypt: Fix buffer over-read in cca_cipher2protkey - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/36b230835b8a008266aad22168ca52afacc8a58d

Vendor Advisories for CVE-2026-68453(1)

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

Data Freshness Timeline

(refreshed 32× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-08-21 03:18 UTCEG score recompute
  2. 2026-08-21 03:18 UTCGHSA enrichment
  3. 2026-08-20 22:56 UTCEPSS rescore
  4. 2026-08-20 14:04 UTCGHSA enrichment
  5. 2026-08-20 00:38 UTCEG score recompute
  6. 2026-08-20 00:38 UTCGHSA enrichment
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 11:26 UTCGHSA enrichment
  9. 2026-08-18 22:14 UTCEG score recompute
  10. 2026-08-18 22:14 UTCGHSA enrichment
  11. 2026-08-18 13:49 UTCEPSS rescore
  12. 2026-08-18 13:49 UTCEPSS rescore
  13. 2026-08-18 08:59 UTCGHSA enrichment
  14. 2026-08-17 19:46 UTCEG score recompute
  15. 2026-08-17 19:45 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 06:30 UTCEG score recompute
  18. 2026-08-17 06:30 UTCGHSA enrichment
  19. 2026-08-17 05:35 UTCEG score recompute
  20. 2026-08-17 05:35 UTCGHSA enrichment
  21. 2026-08-16 17:42 UTCEG score recompute
  22. 2026-08-16 17:42 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 04:31 UTCEG score recompute
Show 15 more
  1. 2026-08-16 04:31 UTCGHSA enrichment
  2. 2026-08-15 15:20 UTCGHSA enrichment
  3. 2026-08-15 02:08 UTCEG score recompute
  4. 2026-08-15 02:08 UTCGHSA enrichment
  5. 2026-08-15 01:30 UTCEPSS rescore
  6. 2026-08-14 12:57 UTCEG score recompute
  7. 2026-08-14 12:57 UTCGHSA enrichment
  8. 2026-08-13 23:46 UTCEG score recompute
  9. 2026-08-13 23:46 UTCGHSA enrichment
  10. 2026-08-13 23:03 UTCEG score recompute 7.10
  11. 2026-08-13 23:03 UTCGHSA enrichment
  12. 2026-08-13 23:03 UTCMITRE cvelistV5CVSS v3 → 7.1 · severity → HIGH
  13. 2026-08-13 15:22 UTCNVD update
  14. 2026-08-13 14:22 UTCEG score recompute
  15. 2026-08-13 14:21 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-68453?
CVE-2026-68453 is a high vulnerability published on August 13, 2026. In the Linux kernel, the following vulnerability has been resolved: s390/zcrypt: Fix buffer over-read in cca_cipher2protkey Add validation of both the actual key buffer size and token length fields in all the ccachecksec*token() functions. Additionally check in cca_gencipherkey() for possible…
When was CVE-2026-68453 disclosed?
CVE-2026-68453 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68453 actively exploited?
CVE-2026-68453 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.2% of all scored CVEs.
What is the CVSS score of CVE-2026-68453?
CVE-2026-68453 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-68453?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68453, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-68453?

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