CVE-2026-95849linkwarden OS command injection
CVE-2026-95849 is a OS command injection in linkwarden, rated medium (6.8 on CVSS 3.1).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Received
What it is
Input reaches an operating-system command line, letting an attacker run their own commands on the host. Input is evaluated as code by the application, so an attacker's code runs inside it.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.
What an attacker gains
A successful attack can change data or behaviour. In practice, this kind of flaw lets an attacker run commands or code with the privileges of the affected service. The damage can spread past the vulnerable component into others.
Is it being exploited?
CISA's SSVC assessment notes a public proof of concept.
What to do
- Upgrade linkwarden to 2.15.0 or later.
- Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
- Template engines. The flaw sits between untrusted input and code or command execution.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
- Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.
Questions to answer about your own systems
- Where does linkwarden run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.