CVE-2026-3336

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:amzn, epss
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Improper certificate validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass certificate chain verification when processing PKCS7 objects with multiple signers, except the final signer.

Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version 1.69.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

Published

March 2, 2026

Last Modified

August 21, 2026

Advisory Details (7)

Auto-updated Jul 7, 2026
Patch available. Sources: github_release, github, redhat.
redhatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-3336.json
redhatMentions a patch (unverified)

2444026 – (CVE-2026-3336) CVE-2026-3336 aws-lc: aws-lc: Certificate validation bypass via improper handling of PKCS7 objects

https://bugzilla.redhat.com/show_bug.cgi?id=2444026
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/CVE-2026-3336
redhatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:5459
githubMentions a patch (unverified)

PKCS7_verify Certificate Chain Validation Bypass in AWS-LC · Advisory · aws/aws-lc · GitHub

https://github.com/aws/aws-lc/security/advisories/GHSA-cfwj-9wp5-wqvp
github_release Patch Available

v1.69.0

Patch available: aws/aws-lc v1.69.0

https://github.com/aws/aws-lc/releases/tag/v1.69.0
generic

Issue with AWS-LC: an open-source, general-purpose cryptographic library

https://aws.amazon.com/security/security-bulletins/2026-005-AWS/

Vendor Advisories for CVE-2026-3336(3)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhtas/tuftool-rhel9:17733073092026-03-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFix by version rangeDependents
aws-lc-sys—
  • 0.24.0 up to 0.38.0: fixed in 0.38.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 25× 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.

Showing the most recent 100 of 125 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-3336?
CVE-2026-3336 is a high vulnerability published on March 2, 2026. Improper certificate validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass certificate chain verification when processing PKCS7 objects with multiple signers, except the final signer. Customers of AWS services do not need to take action. Applications using AWS-LC should…
When was CVE-2026-3336 disclosed?
CVE-2026-3336 was first published on March 2, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-3336 actively exploited?
CVE-2026-3336 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-3336?
CVE-2026-3336 has a CVSS base score of 7.5 (the CNA's own assessment, by amzn; NVD's own analysis pending).
How do I remediate CVE-2026-3336?
A fix for CVE-2026-3336 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-3336 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-3336

Explore →

Is Your Infrastructure Affected by CVE-2026-3336?

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

Book a Demo →Browse All CVEs