CVE-2026-23886

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 68% 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: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

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

Swift W3C TraceContext is a Swift implementation of the W3C Trace Context standard, and Swift OTel is an OpenTelemetry Protocol (OTLP) backend for Swift Log, Swift Metrics, and Swift Distributed Tracing. Prior to Swift W3C TraceContext version 1.0.0-beta.5 and Swift OTel version 1.0.4, a denial-of-service vulnerability due to improper input validation allows a remote attacker to crash the service via a malformed HTTP header. This allows crashing the process with data coming from the network when used with, for example, an HTTP server. Most common way of using Swift W3C Trace Context is through Swift OTel. Version 1.0.0-beta.5 of Swift W3C TraceContext and version 1.0.4 of Swift OTel contain a patch for this issue. As a workaround, disable either Swift OTel or the code that extracts the trace information from an incoming header (such as a TracingMiddleware).

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

Published

January 19, 2026

Last Modified

June 17, 2026

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 44× 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 127 total refreshes for this CVE.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-23886?
CVE-2026-23886 is a medium vulnerability published on January 19, 2026. Swift W3C TraceContext is a Swift implementation of the W3C Trace Context standard, and Swift OTel is an OpenTelemetry Protocol (OTLP) backend for Swift Log, Swift Metrics, and Swift Distributed Tracing. Prior to Swift W3C TraceContext version 1.0.0-beta.5 and Swift OTel version 1.0.4, a…
When was CVE-2026-23886 disclosed?
CVE-2026-23886 was first published in the National Vulnerability Database on January 19, 2026, with the most recent update on June 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-23886 actively exploited?
CVE-2026-23886 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 68.1% of all scored CVEs.
What is the CVSS score of CVE-2026-23886?
CVE-2026-23886 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-23886?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23886, 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-23886

Explore →

Is Your Infrastructure Affected by CVE-2026-23886?

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

Start Free Scan →Browse All CVEs