CVE-2026-38979

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

Score 5.4 from GitHub Security Advisory published 2026-07-07. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.4
EG Score
5.4(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
5.5%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 9, 2026

Advisory Details (2)

Auto-updated Jul 9, 2026
Patch available. Sources: github_commit.
generic

GitHub - ajenti/ajenti: Ajenti Core and stock plugins · GitHub

https://github.com/ajenti/ajenti
github_commit Patch Available

commit e54e83888fc7 (ajenti/ajenti)

Patch available: ajenti/ajenti v2.2.15 (contains commit e54e83888fc7)

https://github.com/ajenti/ajenti/commit/e54e83888fc7cb10061a18b04c1a7e3100d77f03

Vendor Advisories for CVE-2026-38979(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:10 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:24 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 22:41 UTCGHSA enrichment
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 00:59 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 03:17 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-14 05:32 UTCGHSA enrichment
  18. 2026-07-13 22:30 UTCEPSS rescore
  19. 2026-07-13 07:49 UTCGHSA enrichment
  20. 2026-07-13 06:13 UTCEPSS rescore
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-12 10:07 UTCGHSA enrichment
  23. 2026-07-12 05:46 UTCEPSS rescore
  24. 2026-07-11 12:24 UTCGHSA enrichment
  25. 2026-07-11 08:27 UTCEPSS rescore
Show 10 more
  1. 2026-07-10 14:41 UTCGHSA enrichment
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-09 16:58 UTCEG score recompute▲ 5.40
  4. 2026-07-09 16:58 UTCGHSA enrichment
  5. 2026-07-09 15:35 UTCMITRE cvelistV5CVSS v3 → 5.4 · severity → MEDIUM
  6. 2026-07-08 15:15 UTCEPSS rescore
  7. 2026-07-07 13:46 UTCEPSS rescore
  8. 2026-07-06 22:49 UTCNVD update
  9. 2026-07-06 21:45 UTCEG score recompute
  10. 2026-07-06 21:44 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-38979?
CVE-2026-38979 is a medium vulnerability published on July 6, 2026. 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…
When was CVE-2026-38979 disclosed?
CVE-2026-38979 was first published in the National Vulnerability Database on July 6, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-38979 actively exploited?
CVE-2026-38979 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-38979?
CVE-2026-38979 has a CVSS v3.1 base score of 5.4 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-38979?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-38979, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-38979

Explore →

Is Your Infrastructure Affected by CVE-2026-38979?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs