CVE-2026-3338

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
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 0

A fix is available — apply it.

Improper signature validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass signature verification when processing PKCS7 objects with Authenticated Attributes.

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.5(medium)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

March 2, 2026

Last Modified

August 21, 2026

Advisory Details (7)

Auto-updated Jul 7, 2026
🔬 Proof of concept available. Patch available. Sources: github_release, github, redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-3338.json
redhat Patch Available

2444025 – (CVE-2026-3338) CVE-2026-3338 aws-lc: AWS-LC: Signature bypass due to improper validation in PKCS7_verify()

https://bugzilla.redhat.com/show_bug.cgi?id=2444025
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-3338
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:5459
github Patch Available🟡 PoC Available

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

https://github.com/aws/aws-lc/security/advisories/GHSA-jchq-39cv-q4wj
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-3338(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 / EcosystemFixed in / 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 rangeFixed inDependents
aws-lc-sys—0.38.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 55× 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-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 12:32 UTCEG score recompute
  4. 2026-08-21 12:32 UTCVendor advisory
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 01:30 UTCEPSS rescore
  12. 2026-08-14 21:01 UTCVendor advisory
  13. 2026-08-14 08:42 UTCEG score recompute
  14. 2026-08-14 08:42 UTCVendor advisory
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-13 00:32 UTCEG score recompute
  17. 2026-08-13 00:32 UTCVendor advisory
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 23:23 UTCEG score recompute
  20. 2026-08-11 23:23 UTCVendor advisory
  21. 2026-08-11 13:43 UTCEPSS rescore
  22. 2026-08-11 05:56 UTCEG score recompute
  23. 2026-08-11 05:56 UTCVendor advisory
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 08:00 UTCVendor advisory
Show 63 more
  1. 2026-08-09 19:59 UTCEG score recompute
  2. 2026-08-09 19:59 UTCVendor advisory
  3. 2026-08-09 13:46 UTCEPSS rescore
  4. 2026-08-09 08:19 UTCEG score recompute
  5. 2026-08-09 08:19 UTCVendor advisory
  6. 2026-08-08 16:37 UTCEPSS rescore
  7. 2026-08-08 07:54 UTCVendor advisory
  8. 2026-08-07 20:15 UTCEG score recompute
  9. 2026-08-07 20:15 UTCVendor advisory
  10. 2026-08-06 13:46 UTCEPSS rescore
  11. 2026-08-06 02:49 UTCEG score recompute
  12. 2026-08-06 02:49 UTCVendor advisory
  13. 2026-08-05 19:17 UTCEPSS rescore
  14. 2026-08-04 15:10 UTCEPSS rescore
  15. 2026-08-04 10:38 UTCEPSS rescore
  16. 2026-08-04 04:34 UTCEG score recompute
  17. 2026-08-04 04:34 UTCVendor advisory
  18. 2026-08-03 10:36 UTCEPSS rescore
  19. 2026-08-02 19:09 UTCEG score recompute
  20. 2026-08-02 19:09 UTCVendor advisory
  21. 2026-08-02 02:27 UTCEPSS rescore
  22. 2026-08-01 04:16 UTCEPSS rescore
  23. 2026-07-30 16:28 UTCEPSS rescore
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-26 14:54 UTCEPSS rescore
  26. 2026-07-26 14:54 UTCEPSS rescore
  27. 2026-07-25 14:18 UTCEPSS rescore
  28. 2026-07-25 14:18 UTCEPSS rescore
  29. 2026-07-24 14:17 UTCEPSS rescore
  30. 2026-07-24 14:17 UTCEPSS rescore
  31. 2026-07-23 14:18 UTCEPSS rescore
  32. 2026-07-23 14:18 UTCEPSS rescore
  33. 2026-07-23 03:09 UTCEG score recompute
  34. 2026-07-22 14:08 UTCEPSS rescore
  35. 2026-07-21 15:24 UTCEPSS rescore
  36. 2026-07-20 17:08 UTCEPSS rescore
  37. 2026-07-19 14:31 UTCEPSS rescore
  38. 2026-07-19 02:29 UTCEPSS rescore
  39. 2026-07-18 10:04 UTCEPSS rescore
  40. 2026-07-18 06:59 UTCOSV refresh
  41. 2026-07-16 17:03 UTCEPSS rescore
  42. 2026-07-15 16:57 UTCEPSS rescore
  43. 2026-07-15 16:57 UTCEPSS rescore
  44. 2026-07-15 02:00 UTCEPSS rescore
  45. 2026-07-13 22:30 UTCEPSS rescore
  46. 2026-07-13 06:13 UTCEPSS rescore
  47. 2026-07-13 06:13 UTCEPSS rescore
  48. 2026-07-12 05:46 UTCEPSS rescore
  49. 2026-07-11 08:27 UTCEPSS rescore
  50. 2026-07-09 19:10 UTCEPSS rescore
  51. 2026-07-08 15:15 UTCEPSS rescore
  52. 2026-07-07 13:46 UTCEPSS rescore
  53. 2026-07-06 16:27 UTCEPSS rescore
  54. 2026-07-06 16:27 UTCEPSS rescore
  55. 2026-07-06 02:23 UTCEPSS rescore
  56. 2026-07-06 02:23 UTCEPSS rescore
  57. 2026-07-05 02:30 UTCEPSS rescore
  58. 2026-07-04 06:31 UTCEPSS rescore
  59. 2026-07-01 15:06 UTCEPSS rescore
  60. 2026-06-30 23:22 UTCEPSS rescore
  61. 2026-06-30 04:35 UTCEG score recompute
  62. 2026-06-30 04:35 UTCVendor advisory
  63. 2026-06-30 04:31 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-3338?
CVE-2026-3338 is a high vulnerability published on March 2, 2026. Improper signature validation in PKCS7_verify() in AWS-LC allows an unauthenticated user to bypass signature verification when processing PKCS7 objects with Authenticated Attributes. Customers of AWS services do not need to take action. Applications using AWS-LC should upgrade to AWS-LC version…
When was CVE-2026-3338 disclosed?
CVE-2026-3338 was first published in the National Vulnerability Database 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-3338 actively exploited?
CVE-2026-3338 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.8% of all scored CVEs.
What is the CVSS score of CVE-2026-3338?
CVE-2026-3338 has a CVSS v4.0 base score of 7.5 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-3338?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-3338, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-3338?

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

Start Free Scan →Browse All CVEs