Security readout for executives and security teams
Plain-English summary
Bun before 1.3.5 could be tricked into trusting a non-npm dependency if it used the same name as an entry on Bun’s default trusted-dependencies list. This is a software supply-chain risk for development and CI environments that install dependencies from file, link, git, or GitHub sources.
Executive priority
Treat this as a near-term supply-chain hygiene issue, not an emergency based on current evidence. Patch build and developer environments promptly because integrity impact in dependency installation can affect software delivery pipelines.
Technical view
CVE-2026-24910 is a CWE-348 issue in Bun’s default trust allow list. A non-npm package with a matching name, delivered through file, link, git, or github dependency forms, could spoof trusted status. The CVSS 3.1 score is 5.9 with high integrity impact and local attack vector.
Likely exposure
Organizations using Bun before 1.3.5 are most exposed in developer machines, build systems, and CI pipelines that install non-registry dependencies from file, link, git, or GitHub references.
Exploitation context
The source bundle does not show CISA KEV listing or confirmed active exploitation. Public reporting frames this as part of broader JavaScript package-manager supply-chain research, but this CVE’s exploitation evidence is limited in the provided sources.
Researcher notes
The CVE record states Bun before 1.3.5 is affected. The affected-version metadata in the bundle is sparse, so rely on the description and Bun 1.3.5 reference. No exploit code, confirmed exploitation, or KEV status is provided.
Mitigation direction
- Upgrade Bun to version 1.3.5 or later.
- Prioritize CI runners and developer environments using Bun.
- Review projects using file, link, git, or GitHub dependencies.
- Avoid untrusted non-registry dependencies where practical.
- Check Bun vendor guidance for any additional configuration advice.
Validation and detection
- Inventory Bun versions across developer workstations and CI systems.
- Identify package manifests using file, link, git, or GitHub dependency references.
- Review Bun lockfiles and dependency sources for unexpected non-registry packages.
- Confirm Bun reports version 1.3.5 or later after remediation.
- Monitor vendor and CVE records for updated guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-348: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-24910 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N1.44Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Less Trusted Source
Use of Less Trusted Source represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.