CVE
HyperFrames before 0.8.73 Path Traversal via Studio Waveform and Thumbnail Routes
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 0.8.73
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.8.73.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 19/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
HyperFrames before 0.8.73 contains a path traversal vulnerability in the Studio server waveform and thumbnail routes that percent-decode paths without containment checks. Unauthenticated attackers, including script in a malicious composition, can send encoded ../ sequences to probe file existence and extract waveform data from files outside the project.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach10/20Affects npm packages
- Severity2.3/10CVSS 2.3
- No patch0/5No signal
What would change the score
- Would score about 74 if added to CISA KEV
- Would score about 69 if CISA's SSVC rates exploitation active
- Would score about 34 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.8.73.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130842 (HyperFrames before 0.8.73 Path Traversal via Studio Waveform and Thumbnail Routes), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130842 (entry last updated 2026-11-17):
Affected:
- npm package hyperframes: fixed in 0.8.73
Fixed versions: 0.8.73.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-130842 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130842 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/heygen-com/hyperframes/commit/fed45bac7c1623fd2b2979b9d2d86f647cd980b4
- https://github.com/heygen-com/hyperframes/blob/v0.8.31/packages/studio-server/src/routes/waveform.ts#L17-L22
- https://github.com/heygen-com/hyperframes/blob/v0.8.31/packages/studio-server/src/routes/thumbnail.ts#L87-L130
- https://www.vulncheck.com/advisories/hyperframes-before-0.8.73-path-traversal-via-studio-waveform-and-thumbnail-routes
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130842
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130842"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- hyperframesnpm
fixed in 0.8.73
Evidence 6
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 4
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130842
Is CVE-2026-130842 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-130842?
hyperframes (npm): before 0.8.73.Source: cve.now feed data
How do I fix CVE-2026-130842?
Upgrade to a fixed version: 0.8.73.Source: cve.now feed data