Skip to main content
VulnerabilityPublished

CVE-2026-95849: linkwarden · OS Command Injection

Affects linkwardenSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.8 Medium : upgrade to 2.15.0 when convenient.

Data as of 17 Nov 2026, 19:21 UTC

CVSS 3.1 base score
6.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.8
Patch
Available – fixed in 2.15.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade linkwarden to 2.15.0.

Affected software

ProductAffectedFixed in
linkwardenlinkwardenAffected
  • <2.15.0
Fixed in
  • 2.15.0

AI-suggested

Upgrade Linkwarden to version 2.15.0 or later, where this vulnerability is fixed. The fix involves properly sanitizing and quoting the github.head_ref branch name in the GitHub Actions workflow to prevent command injection. No other mitigation is necessary once the upgrade is applied.

Description

Linkwarden versions prior to 2.15.0 contain an OS command injection vulnerability in the GitHub Actions workflow check-branch.yml. This workflow runs on the privileged pull_request_target event and unsafely interpolates the attacker-controlled source branch name into a shell script without proper quoting. An unauthenticated attacker can exploit this by opening a pull request from a fork with malicious shell metacharacters in the branch name, leading to arbitrary command execution within the privileged CI job. The job has access to GITHUB_TOKEN and exposed secrets, enabling secret exfiltration and potential repository content modification if token permissions allow. The issue is fixed in version 2.15.0.

References

Community reviews

Loading reviews…