cve.bz

CVE-2026-111922 go-vikunja vikunja

7.2 highEPSS 0.1%

High (7.2) in go-vikunja vikunja. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
Vikunja from 2.2.0 before 2.7.0 contains a permissive CORS configuration that trusts every localhost and 127.0.0.1 port with credentials, even when service.publicurl is set. Attackers controlling a page on any localhost port can send a credentialed request to the token refresh endpoint and read the returned bearer JWT to take over the logged-in user's account.

Severity

CVSS 4.0

7.2 high
CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

6.3 medium
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.10% 30 days ago) estimated probability of exploitation activity in the next 30 days; 4th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-10-19. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
OWASP Top 10
A02:2025 Security Misconfiguration
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-111922 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-111922?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-111922?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-111922 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
go-vikunja vikunjafrom 2.2.0 before 2.7.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-m687-p538-r5hpGocode.vikunja.io/api>=2.2.0 <=2.6.0no fix published
GO-2026-6739Gocode.vikunja.io/apiall versionsno fix published

References

Check your stackJSON