How severe is CVE-2026-27485?

No CVSS score has been assigned to CVE-2026-27485 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-27485?

CVE-2026-27485 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-27485?

Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27485 is resolved across your whole dependency graph.

How do I detect CVE-2026-27485 in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-27485 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2026-27485?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27485 can be triaged on real exposure rather than presence alone.

Is CVE-2026-27485 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-27485 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-27485?

CVE-2026-27485 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-27485?

CVE-2026-27485 is classified as CWE-61 (CWE-61). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-27485 published, and has it been updated?

CVE-2026-27485 was published on February 21, 2026 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-27485 — openclaw

Fix: openclaw/openclaw@c275932

CVE-2026-27485 is a CWE-61 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw affected by Stored XSS in Control UI via unsanitized assistant name/avatar in inline script injection

Also known asGHSA-r6h2-5gqq-v5v6

Published

Feb 21, 2026

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27485.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

133other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.5Mdownloads / week

Description

Vulnerability

skills/skill-creator/scripts/package_skill.py (a local helper script used when authors package skills) previously followed symlinks while building .skill archives.

If an author runs this script on a crafted local skill directory containing symlinks to files outside the skill root, the resulting archive can include unintended file contents.

Severity and Exposure

Severity: Low
Execution context: local/manual workflow only (skill author packaging step)
No remote trigger: this is not reachable via normal OpenClaw gateway/chat runtime paths
No extraction Zip Slip in this finding: this issue is limited to packaging-time symlink following

Impact

Potential unintentional disclosure of local files from the packaging machine into a generated .skill artifact.
Requires local execution of the packaging script on attacker-controlled skill contents.

Affected Components

skills/skill-creator/scripts/package_skill.py

Affected Packages / Versions

Package: openclaw (npm)
Latest published version during triage: 2026.2.17
Vulnerable version range: <= 2026.2.17
Planned patched version (next release): 2026.2.18

Remediation

Reject symlinks during skill packaging.
Add regression tests for symlink file and symlink directory cases.
Update packaging guidance to document the symlink restriction.

Fix Commit(s)

c275932aa4230fb7a8212fe1b9d2a18424874b3f
ee1d6427b544ccadd73e02b1630ea5c29ba9a9f0

Related PR

https://github.com/openclaw/openclaw/pull/20796

Release Process Note

patched_versions is pre-set to the planned next release (2026.2.18). Once npm [email protected] is published, this advisory is ready to publish without additional edits.

Thanks @aether-ai-agent for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.19`npm install openclaw@2026.2.19`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27485 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-27485 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-27485. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Vulnerability `skills/skill-creator/scripts/package_skill.py` (a local helper script used when authors package skills) previously followed symlinks while building `.skill` archives. If an author runs this script on a crafted local skill directory containing symlinks to files outside the skill root, the resulting archive can include unintended file contents. ## Severity and Exposure - **Severity: Low** - **Execution context:** local/manual workflow only (skill author packaging step) - **No remote trigger:** this is not reachable via normal OpenClaw gateway/chat runtime paths - **No extra

O3 Security · Impact-Aware SCA

Is CVE-2026-27485 in your dependencies?

O3 Security finds CVE-2026-27485 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works