How severe is GHSA-m4g2-2q66-vc9v?

No CVSS score has been assigned to GHSA-m4g2-2q66-vc9v yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-m4g2-2q66-vc9v?

GHSA-m4g2-2q66-vc9v affects the following packages: code.vikunja.io/api (Go). Ecosystems affected: Go.

How do I fix GHSA-m4g2-2q66-vc9v?

No patched version of code.vikunja.io/api has shipped for GHSA-m4g2-2q66-vc9v yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-m4g2-2q66-vc9v in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.vikunja.io/api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-m4g2-2q66-vc9v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-m4g2-2q66-vc9v?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m4g2-2q66-vc9v can be triaged on real exposure rather than presence alone.

Is GHSA-m4g2-2q66-vc9v actively exploited in the wild?

No public exploit code has been indexed for GHSA-m4g2-2q66-vc9v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-m4g2-2q66-vc9v?

GHSA-m4g2-2q66-vc9v has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-m4g2-2q66-vc9v?

GHSA-m4g2-2q66-vc9v is classified as CWE-80 (CWE-80), Cross-site Scripting (XSS) (CWE-79). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-m4g2-2q66-vc9v published, and has it been updated?

GHSA-m4g2-2q66-vc9v was published on February 11, 2026 and was last updated on February 19, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-m4g2-2q66-vc9v — api

Fix: go-vikunja/vikunja@dd0b82f

GHSA-m4g2-2q66-vc9v is a CWE-80 vulnerability in code.vikunja.io/api. No vendor fix is recorded yet; mitigation options are listed below.

Vikunja Vulnerable to XSS Via Task Preview

Also known asCVE-2026-25935GO-2026-4480

Published

Feb 11, 2026

Updated

Feb 19, 2026

Affected

1 pkg

Patched

See advisory

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA’s SSVC triage for GHSA-m4g2-2q66-vc9v.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs24th percentile — riskier than 24% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹code.vikunja.io/api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The task preview component creates a unparented div. The div's innerHtml is set to the unescaped description of the task

Details

In the TaskGlanceTooltip.vue it temporarily creates a div and sets the innerHtml to the description here. Since there is no escaping on either the server or client side, a malicious user can share a project, create a malicious task, and cause an XSS on hover.

PoC

Create a project
Create a task with any description
Use the api to update the task with a description containing unescaped HTML (ex: <img src=x onerror="alert(localStorage.getItem('token'))">
Share the project with any permission level
Send malicious project to user and ask them to view task

Impact

Any user on an instance can cause an XSS on another

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`code.vikunja.io/api`	all versions	No fix

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for code.vikunja.io/api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of code.vikunja.io/api has shipped for GHSA-m4g2-2q66-vc9v yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-m4g2-2q66-vc9v can be triaged on real exposure rather than presence alone.

Tailored to GHSA-m4g2-2q66-vc9v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The task preview component creates a unparented div. The div's `innerHtml` is set to the unescaped description of the task ### Details In the `TaskGlanceTooltip.vue` it temporarily creates a div and sets the `innerHtml` to the description [here](https://github.com/go-vikunja/vikunja/blob/cdca79032526966cb248b72bddcf2a0f888c8a8f/frontend/src/components/tasks/partials/TaskGlanceTooltip.vue#L118). Since there is no escaping on either the server or client side, a malicious user can share a project, create a malicious task, and cause an XSS on hover. ### PoC 1. Create a project 2. Cre

O3 Security · Impact-Aware SCA

Is GHSA-m4g2-2q66-vc9v in your dependencies?

O3 Security finds GHSA-m4g2-2q66-vc9v across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works