CVE-2026-74881

CRITICALNVD 9.39.3—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

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

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

openssl_encrypt versions before 1.4.0 configure CORS with allow_origins set to wildcard and allow_credentials enabled to true. Attackers can create malicious websites that make authenticated cross-origin requests to the API on behalf of any user who visits them.

CVSS v3
9.3
EG Score
9.3(medium)
EG Risk
42(Track)
EG Risk 42/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
Severity93% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 17, 2026

Last Modified

September 10, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github.
generic

openssl_encrypt before 1.4.0 CORS Misconfiguration via Wildcard Origins | Advisories | VulnCheck

https://www.vulncheck.com/advisories/openssl-encrypt-before-cors-misconfiguration-via-wildcard-origins
github Patch Available

CORS wildcard with allow_credentials=True in standalone servers · Advisory · jahlives/openssl_encrypt · GitHub

https://github.com/jahlives/openssl_encrypt/security/advisories/GHSA-c65f-x25w-62jv

Vendor Advisories for CVE-2026-74881(1)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
openssl-encrypt0.2.2 ... 1.4.0b8 (44 versions)1.4.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 48× in last 7d / 117× 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 131 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-74881?
CVE-2026-74881 is a critical vulnerability published on August 17, 2026. opensslencrypt versions before 1.4.0 configure CORS with alloworigins set to wildcard and allow_credentials enabled to true. Attackers can create malicious websites that make authenticated cross-origin requests to the API on behalf of any user who visits them.
When was CVE-2026-74881 disclosed?
CVE-2026-74881 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-74881 actively exploited?
CVE-2026-74881 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 83.2% of all scored CVEs.
What is the CVSS score of CVE-2026-74881?
CVE-2026-74881 has a CVSS v3 base score of 9.3 (NVD).
How do I remediate CVE-2026-74881?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-74881, 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-74881

Explore →

Is Your Infrastructure Affected by CVE-2026-74881?

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

Start Free Scan →Browse All CVEs