Arbitrary file write via symlink path traversal
Published Feb 25, 2026 · Updated Feb 25, 2026
Path traversal in Google Dart SDK before 3.11.0 and Flutter SDK before 3.41.0 allows attackers to write files outside PUB_CACHE. The pub tar extractor joins an entry name before normalizing it, so a symlink followed by parent-directory segments passes its destination check but resolves outside the cache. Exposure requires a malicious archive from an untrusted package repository; vetted pub.dev packages, trusted repositories, and git dependencies are unaffected.
Summary
What happened
Path traversal in Google Dart SDK before 3.11.0 and Flutter SDK before 3.41.0 allows attackers to write files outside PUB_CACHE. The pub tar extractor joins an entry name before normalizing it, so a symlink followed by parent-directory segments passes its destination check but resolves outside the cache. Exposure requires a malicious archive from an untrusted package repository; vetted pub.dev packages, trusted repositories, and git dependencies are unaffected.
The record
- CVE
- CVE-2026-27704
- Published
- Feb 25, 2026
- Updated
- Feb 25, 2026
- Vendor
- Go standard library
- Product
- Dart SDK
- Classifications
- CWE-22, T1195.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 25, 2026CVE publishedPublication date reported by the CVE source.
- Feb 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.11.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo