CVE
agent-device remote file read via file:// URLs in open command
agent-device 0.21.36 exposes local files to an authenticated remote caller who can reach the web command surface via /rpc, with the managed agent-browser 0.39.0 backend. Fixed in 0.21.37.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.21.37
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affected agent-device version 0.21.36 (fixed in 0.21.37). Caller has access to the web command surface, through a remote /rpc endpoint. Managed web backend agent-browser 0.39.0 is used, which opens file:// navigation without extra flags. The target file must be readable by the account running the daemon.
- Published
- 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? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- 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
agent-device, a product from callstack, contains a local file disclosure flaw that lets a remote attacker with low-privilege login read any plaintext file the daemon account can access on the host. The attacker reaches it over the network by sending an open command with a file:// URL through the /rpc endpoint, then requesting a snapshot to read the file.
Read the original description
agent-device from 0.21.36 before 0.21.37 contains a local file disclosure vulnerability that allows authenticated remote callers to read daemon-host files by opening file:// URLs. Attackers can send an open command with a file:// target through /rpc, then issue snapshot to read any plaintext file readable by the daemon account.
Who should check
Teams running callstack agent-device 0.21.36 as a remote daemon exposing /rpc with web open and snapshot commands
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Affected agent-device version 0.21.36 (fixed in 0.21.37). Caller has access to the web command surface, through a remote /rpc endpoint. Managed web backend agent-browser 0.39.0 is used, which opens file:// navigation without extra flags. The target file must be readable by the account running the daemon.Upgrade to a fixed version: 0.21.37.
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-129130 (agent-device 0.21.36 Local File Disclosure via file:// Navigation in Open Command), 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-129130 (entry last updated 2026-11-13):
Affected:
- callstack agent-device: from 0.21.36, fixed in 0.21.37
Fixed versions: 0.21.37.
Conditions (all must be true for the bug to be hit):
- Affected agent-device version 0.21.36 (fixed in 0.21.37). (source: https://www.vulncheck.com/advisories/agent-device-0.21.36-local-file-disclosure-via-file-navigation-in-open-command)
- Caller has access to the web command surface, through a remote /rpc endpoint. (source: https://github.com/callstack/agent-device/security/advisories/GHSA-g87j-p64h-w8wc)
- Managed web backend agent-browser 0.39.0 is used, which opens file:// navigation without extra flags. (source: https://github.com/callstack/agent-device/security/advisories/GHSA-g87j-p64h-w8wc)
- The target file must be readable by the account running the daemon. (source: https://github.com/callstack/agent-device/security/advisories/GHSA-g87j-p64h-w8wc)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-129130 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129130 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/callstack/agent-device/security/advisories/GHSA-g87j-p64h-w8wc
- https://github.com/callstack/agent-device/commit/2deb909ec88bbbde615ec7c8f3895ef222d8ab3d
- https://github.com/callstack/agent-device/releases/tag/v0.21.37
- https://github.com/callstack/agent-device/blob/ebbaff9a6be75babdb4adcb9074d7522a2773330/packages/daemon/src/server/remote-host-input-policy.ts#L67
- https://www.vulncheck.com/advisories/agent-device-0.21.36-local-file-disclosure-via-file-navigation-in-open-command
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-129130
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-129130"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- callstack agent-device
From 0.21.36 · fixed in 0.21.37
Evidence 7
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
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-129130
Is CVE-2026-129130 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
What does this mean?
An authenticated remote caller can use file:// navigation in the open command to read plaintext files on the daemon host that the daemon's account can read, such as files at known paths.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-129130?
agent-device: from 0.21.36 before 0.21.37.Source: cve.now feed data
Am I affected, and how do I check?
The range affected is agent-device 0.21.36, fixed in 0.21.37. The exposure also needs the web command surface reachable through a remote /rpc endpoint, the managed agent-browser 0.39.0 backend, and a target file readable by the account running the daemon. To check, compare the installed agent-device version with 0.21.36 and check which agent-browser version the managed backend pins.Source: vulncheck.com, github.com
How do I fix CVE-2026-129130?
Upgrade agent-device to 0.21.37 or later. The facts name no workaround or patch identifiers.Source: vulncheck.com, github.com