CVE-2026-15895
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 · uneditedOS command injection in the npm package loading component in AWS jsii-diff before 1.131.0 might allow context-dependent attackers to execute arbitrary commands via crafted package specifiers passed to the npm: source argument. To mitigate this issue, users should upgrade to jsii-diff v1.131.0 or later.
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 confidenceOS command injection vulnerability in the npm package loading component of AWS jsii-diff allows context-dependent attackers to execute arbitrary commands via crafted package specifiers passed to the npm source argument.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify if jsii-diff is installedRun 'npm list jsii-diff' or check package.json dependencies for the jsii-diff packageAffected if jsii-diff appears in the installed packages or package.json
-
Determine the installed version of jsii-diffRun 'npm list jsii-diff --depth=0' or 'npm view jsii-diff version' to see the version number in your environmentAffected if The version number returned is lower than 1.131.0
-
Verify usage of npm source argument featureSearch project code for invocations of jsii-diff that pass package specifiers to an npm source argument, such as calls to functions that accept a package name or npm source parameterAffected if Code passes user-controlled or unsanitized package specifiers to the npm source argument in jsii-diff
-
Check for presence of malicious package specifiersReview any package specifiers being passed to jsii-diff npm functions for characters that could enable command injection, such as backticks, $(), or shell metacharactersAffected if Package specifiers contain shell injection characters or unexpected command sequences
-
Audit dependency tree for vulnerable versionRun 'npm ls jsii-diff' to see if jsii-diff is a transitive dependency and identify all versions in the dependency treeAffected if Any instance of jsii-diff with version below 1.131.0 is found in the dependency tree
You are affected if jsii-diff version 1.131.0 or higher is not installed and your code uses the npm package loading feature with external package specifiers.
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 jsii-diff to version 1.131.0 or later to remediate this command injection vulnerability.
v1.131.0
- Update the jsii-diff npm package to version 1.131.0 or later by running: npm install jsii-diff@^1.131.0 or npm update jsii-diff
- Verify the installed version using: npm list jsii-diff
- If using jsii-diff as a dependency in another project, update the package.json dependency version to ^1.131.0 and run npm install
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-15895 — 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-15895 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