CVE-2026-54285
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedopentelemetry-js is the OpenTelemetry JavaScript Client. Prior to 2.8.0, W3CBaggagePropagator.extract() in @opentelemetry/core does not enforce size limits when parsing inbound baggage HTTP headers. The W3C Baggage specification recommends a maximum of 8,192 bytes and 180 entries; these limits were only enforced on the outbound (inject()) path, not on the inbound (extract()) path. Parsing oversized baggage causes memory allocation proportional to the header size without any cap. This vulnerability is fixed in 2.8.0.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe W3CBaggagePropagator.extract() method in @opentelemetry/core fails to enforce W3C Baggage specification limits (8,192 bytes max, 180 entries max) on inbound HTTP headers. This allows attackers to send oversized baggage headers causing unbounded memory allocation during parsing, potentially leading to denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate @opentelemetry/core packageRun 'npm list @opentelemetry/core' or check package.json dependencies to find the installed version of @opentelemetry/coreAffected if The package is present in the project dependencies
-
Compare installed version to fixed releaseCheck if the installed version is below 2.8.0 by running 'npm view @opentelemetry/core version' and comparingAffected if Installed version is less than 2.8.0
-
Verify W3CBaggagePropagator is in useSearch codebase for imports or usage of 'W3CBaggagePropagator' and look for calls to the extract() method in propagator setup codeAffected if Code uses W3CBaggagePropagator.extract() for processing inbound HTTP headers
-
Confirm application accepts HTTP requests with Baggage headersInspect HTTP server configuration to see if incoming request headers containing 'baggage' are parsed and processedAffected if Application processes inbound HTTP requests and extracts baggage headers from them
User is affected if @opentelemetry/core version is below 2.8.0 and the application uses W3CBaggagePropagator.extract() to process inbound HTTP headers containing baggage.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade @opentelemetry/core to version 2.8.0 or later to enforce baggage size limits on the extract() path.
2.8.0 or later
- Check current version of @opentelemetry/core in your project by running: npm list @opentelemetry/core
- Upgrade @opentelemetry/core to version 2.8.0 or later using: npm install @opentelemetry/core@^2.8.0
- Verify the upgrade was successful by running: npm list @opentelemetry/core
- Rebuild and test your application to ensure the baggage propagator works correctly with the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54285 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54285 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data