GHSA-MVPQ-2V8X-WW6G

Vulnerability from github – Published: 2026-01-21 01:05 – Updated: 2026-01-21 01:05
VLAI?
Summary
Swift W3C TraceContext vulnerable to a malformed HTTP header causing a crash
Details

Impact

A denial-of-service vulnerability due to improper input validation allows a remote attacker to crash the service via a malformed HTTP header.

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.

Patches

https://github.com/swift-otel/swift-w3c-trace-context/commit/5da9b143ba6046734de3fa51dafea28290174e4e

Workarounds

Disable either Swift OTel or the code that extracts the trace information from an incoming header (such as a TracingMiddleware).

References

Swift W3C TraceContext 1.0.0-beta.5 Swift OTel 1.0.4

Severity ?
5.3 (Medium)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "SwiftURL",
        "name": "github.com/swift-otel/swift-w3c-trace-context"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.0.0-beta.5"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "SwiftURL",
        "name": "github.com/swift-otel/swift-otel"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.0.4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-23886"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-20"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-01-21T01:05:09Z",
    "nvd_published_at": "2026-01-19T21:15:52Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nA denial-of-service vulnerability due to improper input validation allows a remote attacker to crash the service via a malformed HTTP header.\n\nAllows 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.\n\n### Patches\n\nhttps://github.com/swift-otel/swift-w3c-trace-context/commit/5da9b143ba6046734de3fa51dafea28290174e4e\n\n### Workarounds\nDisable either Swift OTel or the code that extracts the trace information from an incoming header (such as a `TracingMiddleware`).\n\n### References\n\n[Swift W3C TraceContext 1.0.0-beta.5](https://github.com/swift-otel/swift-w3c-trace-context/releases/tag/1.0.0-beta.5)\n[Swift OTel 1.0.4](https://github.com/swift-otel/swift-otel/releases/tag/1.0.4)",
  "id": "GHSA-mvpq-2v8x-ww6g",
  "modified": "2026-01-21T01:05:09Z",
  "published": "2026-01-21T01:05:09Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/swift-otel/swift-w3c-trace-context/security/advisories/GHSA-mvpq-2v8x-ww6g"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-23886"
    },
    {
      "type": "WEB",
      "url": "https://github.com/swift-otel/swift-w3c-trace-context/commit/5da9b143ba6046734de3fa51dafea28290174e4e"
    },
    {
      "type": "WEB",
      "url": "https://github.com/swift-otel/swift-otel/releases/tag/1.0.4"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/swift-otel/swift-w3c-trace-context"
    },
    {
      "type": "WEB",
      "url": "https://github.com/swift-otel/swift-w3c-trace-context/releases/tag/1.0.0-beta.5"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Swift W3C TraceContext vulnerable to a malformed HTTP header causing a crash"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Detection rules are retrieved from Rulezet.