What is CVE-2026-38979?
ajenti through v2.2.13 has a clickjacking weakness in the browser-facing login and administrative UI. In ajenti-core/aj/http.py, the core HTTP response path initializes an empty header list, forwards handler-added headers verbatim, and finalizes responses through WSGI start_response() without adding anti-framing protections such as X-Frame-Options or a Content-Security-Policy frame-ancestors restriction.
The identifier was first published 91 days ago.
Severity and exploitation probability
- EPSS (FIRST)
- 0.1% probability of exploitation in the next 30 days, higher than 4.1% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 0.2/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-07-06
Is CVE-2026-38979 being exploited?
It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.
Affected products and versions
No affected-product or package list has been recorded for CVE-2026-38979 in the tracked sources. The vendor advisory and the references below are the authoritative statement of what is affected.
How to fix CVE-2026-38979
No vendor patch reference has been recorded for CVE-2026-38979 in the tracked sources. Follow the references below for a fix, and treat any affected deployment as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-38979
No threat campaign in the Threadlinqs corpus currently references CVE-2026-38979, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, NVD, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.