Vulnerable Library - @forgerock/mock-api-v2-1.0.0.tgz
Path to vulnerable library: /package.json
Found in HEAD commit: d5561ef9999f1798c0c700b35a14e39937f92c87
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: d5561ef9999f1798c0c700b35a14e39937f92c87
Found in base branch: main
Vulnerability Details
opentelemetry-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.
Publish Date: 2026-06-22
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: d5561ef9999f1798c0c700b35a14e39937f92c87
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: d5561ef9999f1798c0c700b35a14e39937f92c87
Found in base branch: main
Vulnerability Details
opentelemetry-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.
Publish Date: 2026-06-22
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