# CVE-2026-30916: Withdrawn Advisory: Shescape has possible misidentification of shell due to link chains


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Mar 2026
- **Updated:** 20 Mar 2026
- **Also known as:** GHSA-6f6w-6j58-rq76

## What is CVE-2026-30916?

CVE-2026-30916 is a vulnerability in shescape, published on 9 Mar 2026. 

### Official description

** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: Further investigation determined that the software behavior described did not falls within the project's threat model. See https://github.com/github/advisory-database/pull/7206 for more information.

## Which versions are affected by CVE-2026-30916?

2 open source packages ship an affected version, including shescape.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shescape` | npm | All versions | 2.1.9 |
| `shescape` | npm | All versions | 2.1.9 |

## How do I fix CVE-2026-30916?

Upgrade shescape to 2.1.9 or later.

## Is CVE-2026-30916 being exploited?

There is no known exploitation of CVE-2026-30916 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30916 and fix it if it is affected.

What it is: CVE-2026-30916 is a vulnerability in shescape, published on 9 Mar 2026. 
Exploitation: There is no known exploitation of CVE-2026-30916 in the wild and no public exploit code.

Affected packages and fixed versions:
- shescape (npm): affected all versions; fixed in 2.1.9
- shescape (npm): affected all versions; fixed in 2.1.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30916/ (Markdown: https://insights.sbomify.com/CVE-2026-30916/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30916
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30916
- OSV: https://osv.dev/vulnerability/CVE-2026-30916

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30916/
Summaries are generated and may contain mistakes; the official description above is the record.