Skip to content
Applications

CVE-2026-59261

8.4
High
EPSS 0.27%Patch availableJul 9, 2026

Workspace dotenv files can override provider credentials and leak secrets.

common questions

Is CVE-2026-59261 being exploited?

Not confirmed. CVE-2026-59261 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.27% probability of exploitation in the next 30 days.

How severe is CVE-2026-59261?

CVE-2026-59261 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-59261?

Yes. A fix has been recorded for CVE-2026-59261. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-59261 affect?

CVE-2026-59261 affects OpenClaw <2026.5.28, Developer workspaces using dotenv files, CI/CD pipelines and IaC workflows. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59261?

Upgrade to 2026.5.28, restrict input paths, and rotate any exposed credentials

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
OpenClaw <2026.5.28Developer workspaces using dotenv filesCI/CD pipelines and IaC workflows
impact

Low-trust users can override dotenv to expose provider credentials, enabling account takeover, secret theft, and resource or data compromise.

action required

Patch when possible

affected versions
OpenClaw OpenClaw
  • affected< 2026.5.28

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free