CVE-2026-86542: knowns before 0.30.0 Path Traversal via Import Name
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.74% (FIRST EPSS); higher than 55.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: knowns-dev knowns 0.30.0.
Low priority for now. Upgrade to knowns-dev knowns 0.30.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
knowns before 0.30.0 fails to validate import names in the import routes, allowing unauthenticated attackers to write files outside the imports directory. Attackers can supply traversal sequences in the name parameter to escape the imports directory and overwrite arbitrary files writable by the server process.
- Published
- Sep 7, 2026
- Updated
- Sep 24, 2026
- EPSS
- 0.7% · 55th percentile
- CWE
- CWE-22
Report tools
Action score
35
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · VulnCheck
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (VulnCheck). Independent of NVD's CPE analysis and usually ahead of it.
knowns-dev knowns
- 0.30.0not affected
- before 0.30.0affected · semver
Same product
knowns-dev: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-88899knowns before 0.31.0 External Control of Agent Working Directory via x-opencode-directory Header37Monitor
- CVE-2026-86543knowns before 0.30.0 Unauthenticated Management API Exposure37Monitor
- CVE-2026-86775knowns before 0.30.0 Path Traversal via Document API35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-86540Sep 7, 2026 · knowns before 0.30.0 Arbitrary Code Execution via LSP Binary34Monitor
- ← EarlierCVE-2026-86541Sep 7, 2026 · knowns before 0.30.0 Path Traversal via code.replace MCP action28Monitor
- Later →CVE-2026-86544Sep 7, 2026 · knowns before 0.30.0 Authorization Bypass via Misclassified Code Actions28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| knowns-dev knowns | 0.30.0 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-867752 days apartknowns before 0.30.0 Path Traversal via Document API35Monitor
- CVE-2026-864390 days apartknowns before 0.30.0 Path Traversal via MCP doc and memory tools34Monitor
- CVE-2026-865380 days apartknowns before 0.30.0 Path Traversal via templateFile parameter34Monitor
- CVE-2026-889373 days apartknowns through 0.33.0 Path Traversal via Template Engine34Monitor
- CVE-2026-865410 days apartknowns before 0.30.0 Path Traversal via code.replace MCP action28Monitor
- CVE-2026-889383 days apartknowns through 0.33.0 Path Traversal via code.find MCP tool28Monitor
Not on record for this CVE: public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- github.com/knowns-dev/knowns/blob/v0.29.1/internal/server/routes/imports.go#L519-L551
- github.com/knowns-dev/knowns/commit/d3989829fb5095666d23d005b2f78a082832a396
- github.com/knowns-dev/knowns/releases/tag/v0.30.0
- github.com/knowns-dev/knowns/security/advisories/GHSA-wh3c-v55g-qfg8
- www.vulncheck.com/advisories/knowns-before-0.30.0-path-traversal-via-import-name
Vendor advisories and official records. Exploit/PoC links are deliberately left out.