Vulnerable Library - @forgerock/mock-api-v2-1.0.0.tgz
Path to vulnerable library: /package.json
Found in HEAD commit: ee8c7aafbe3b941a4da35bf641d2e93842f23673
Vulnerabilities
| Vulnerability |
Severity |
 CVSS |
Dependency |
Type |
Fixed in (@forgerock/mock-api-v2 version) |
Remediation Possible** |
| CVE-2026-54285 |
 Medium |
5.3 |
core-2.2.0.tgz |
Transitive |
N/A* |
❌ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2026-54285
Vulnerable Library - core-2.2.0.tgz
OpenTelemetry Core provides constants and utilities shared by all OpenTelemetry SDK packages.
Library home page: https://registry.npmjs.org/@opentelemetry/core/-/core-2.2.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
- @forgerock/mock-api-v2-1.0.0.tgz (Root Library)
- sdk-trace-base-2.2.0.tgz
- ❌ core-2.2.0.tgz (Vulnerable Library)
Found in HEAD commit: ee8c7aafbe3b941a4da35bf641d2e93842f23673
Found in base branch: main
Vulnerability Details
Overview "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. Impact The practical availability impact for most Node.js deployments is limited. Node.js enforces a default "--max-http-header-size" of 16,384 bytes on the total combined size of all HTTP headers, constraining what an external attacker can deliver before the propagator is reached. Additionally, the header is already in memory (parsed by the HTTP layer) by the time it reaches the propagator - the additional allocation is the overhead of splitting into entry objects, not an unbounded read. The risk is higher when transport-layer limits are absent - e.g., non-HTTP transports (messaging systems, custom "TextMapGetter" implementations) or deployments that have raised "--max-http-header-size". Remediation Update "@opentelemetry/core" to version 2.8.0 or later. The fix enforces limits consistent with the W3C Baggage specification at the propagator level: - Maximum total baggage size: 8,192 bytes - Maximum number of entries: 180 - Maximum per-entry size: 4,096 bytes Headers that exceed these limits are truncated at the point the limit is reached. Workarounds Ensure header size limits are configured at the server or gateway level. The default Node.js HTTP header limit (16 KB) mitigates external attack vectors independently of this fix. For non-HTTP transports receiving baggage from untrusted sources, validate input size before passing it to the propagator. References - "W3C Baggage Specification - Limits" (https://www.w3.org/TR/baggage/#limits) - opentelemetry-java: "GHSA-rcgg-9c38-7xpx" (GHSA-rcgg-9c38-7xpx) - opentelemetry-go: "GHSA-mh2q-q3fh-2475" (GHSA-mh2q-q3fh-2475) Credit Reported by tonghuaroot.
Publish Date: 2026-06-15
URL: CVE-2026-54285
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2026-06-15
Fix Resolution: https://github.com/open-telemetry/opentelemetry-js.git - v2.8.0
Path to vulnerable library: /package.json
Found in HEAD commit: ee8c7aafbe3b941a4da35bf641d2e93842f23673
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - core-2.2.0.tgz
OpenTelemetry Core provides constants and utilities shared by all OpenTelemetry SDK packages.
Library home page: https://registry.npmjs.org/@opentelemetry/core/-/core-2.2.0.tgz
Path to dependency file: /package.json
Path to vulnerable library: /package.json
Dependency Hierarchy:
Found in HEAD commit: ee8c7aafbe3b941a4da35bf641d2e93842f23673
Found in base branch: main
Vulnerability Details
Overview "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. Impact The practical availability impact for most Node.js deployments is limited. Node.js enforces a default "--max-http-header-size" of 16,384 bytes on the total combined size of all HTTP headers, constraining what an external attacker can deliver before the propagator is reached. Additionally, the header is already in memory (parsed by the HTTP layer) by the time it reaches the propagator - the additional allocation is the overhead of splitting into entry objects, not an unbounded read. The risk is higher when transport-layer limits are absent - e.g., non-HTTP transports (messaging systems, custom "TextMapGetter" implementations) or deployments that have raised "--max-http-header-size". Remediation Update "@opentelemetry/core" to version 2.8.0 or later. The fix enforces limits consistent with the W3C Baggage specification at the propagator level: - Maximum total baggage size: 8,192 bytes - Maximum number of entries: 180 - Maximum per-entry size: 4,096 bytes Headers that exceed these limits are truncated at the point the limit is reached. Workarounds Ensure header size limits are configured at the server or gateway level. The default Node.js HTTP header limit (16 KB) mitigates external attack vectors independently of this fix. For non-HTTP transports receiving baggage from untrusted sources, validate input size before passing it to the propagator. References - "W3C Baggage Specification - Limits" (https://www.w3.org/TR/baggage/#limits) - opentelemetry-java: "GHSA-rcgg-9c38-7xpx" (GHSA-rcgg-9c38-7xpx) - opentelemetry-go: "GHSA-mh2q-q3fh-2475" (GHSA-mh2q-q3fh-2475) Credit Reported by tonghuaroot.
Publish Date: 2026-06-15
URL: CVE-2026-54285
CVSS 3 Score Details (5.3)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Release Date: 2026-06-15
Fix Resolution: https://github.com/open-telemetry/opentelemetry-js.git - v2.8.0