Command execution via privileged CI branch-name interpolation
Published Nov 17, 2026 · Updated Nov 17, 2026
Script injection in Linkwarden before 2.15.0 allows remote attackers to execute commands in privileged CI via crafted branch names. The .github/workflows/check-branch.yml workflow substitutes github.head_ref unquoted into a shell script before comparing branches. Opening a fork pull request triggers privileged execution; exposed secrets are readable, and repository modification depends on token write permissions.
Summary
What happened
Script injection in Linkwarden before 2.15.0 allows remote attackers to execute commands in privileged CI via crafted branch names. The .github/workflows/check-branch.yml workflow substitutes github.head_ref unquoted into a shell script before comparing branches. Opening a fork pull request triggers privileged execution; exposed secrets are readable, and repository modification depends on token write permissions.
The record
- CVE
- CVE-2026-95849
- Published
- Nov 17, 2026
- Updated
- Nov 17, 2026
- Vendor
- Linkwarden
- Product
- Linkwarden
- Classifications
- CWE-78, CWE-94, T1059.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 17, 2026CVE publishedPublication date reported by the CVE source.
- Nov 17, 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=< 2.15.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.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
- Upstream advisory proof of conceptproof of concept · unverified
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Contact us