Rejected escaping bypass via trusted link chains
Published Mar 9, 2026 · Updated Mar 9, 2026
A shell-identification issue in Eric Cornelissen Shescape before 2.1.9 was reported to allow attackers to bypass escaping via a link chain. The resolver followed only one filesystem link, causing it to select escaping rules for the intermediate link name rather than the actual shell. GitHub rejected the CVE because Shescape's threat model treats the required host filesystem and configuration as trusted, so the behavior is not considered a security issue.
Summary
What happened
A shell-identification issue in Eric Cornelissen Shescape before 2.1.9 was reported to allow attackers to bypass escaping via a link chain. The resolver followed only one filesystem link, causing it to select escaping rules for the intermediate link name rather than the actual shell. GitHub rejected the CVE because Shescape's threat model treats the required host filesystem and configuration as trusted, so the behavior is not considered a security issue.
The record
- CVE
- CVE-2026-30916
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- Eric Cornelissen
- Product
- Shescape
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Mar 9, 2026CVE publishedPublication date reported by the CVE source.
- Mar 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.1.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
No sourced classifications are available.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo