CVE-2026-95849 json
Linkwarden: Script injection via `github.head_ref` in privileged `pull_request_target` workflow (.github/workflows/check-branch.yml)
published 8d ago modified 15h ago also EUVD-2026-127197 , GHSA-2xf4-7cpj-c6rq
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository linkwarden/linkwarden. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
Linkwarden is a self-hosted, open-source collaborative bookmark manager to collect, organize and archive webpages. Prior to 2.15.0, .github/workflows/check-branch.yml runs on the privileged pull_request_target event and interpolates the attacker-controlled github.head_ref source branch name unquoted into a run: shell script. An unauthenticated attacker can open a pull request from a fork with shell metacharacters in its branch name, causing arbitrary commands to execute in the base repository's privileged CI job before the branch comparison result matters. The job has access to GITHUB_TOKEN and any exposed secrets, allowing secret exfiltration and, when workflow token permissions allow repository writes, modification of repository content. This issue is fixed in version 2.15.0.
Patch / fix
Is CVE-2026-95849 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N |
Affected products
- linkwarden linkwarden
Classification
References
Sources
- CVE List CVE-2026-95849
- NVD CVE-2026-95849
- Maintainer advisory GHSA-2xf4-7cpj-c6rq
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of linkwarden/linkwarden published their own advisory on GitHub. Reviewed sources take precedence over it.