CVE-2026-67919

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-18. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 5 sources updated this weekElevated
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: Elevated riskExposed: 0

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

An issue in Halo 2.25.4 allows a remote attacker to execute arbitrary code via the PluginEndpoint.java, installFromUri method, and DefaultPluginApplicationContextFactory components

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

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
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
50%
KEV
Not listed

Published

August 17, 2026

Last Modified

August 18, 2026

Advisory Details (2)

Auto-updated Aug 18, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

CVE-2026-67919.md · GitHub

https://gist.github.com/unpredictable21/d392c26986e81a95676f2a370ecb272b
generic

halo/README.md at main · halo-dev/halo · GitHub

https://github.com/halo-dev/halo/blob/main/README.md

Vendor Advisories for CVE-2026-67919(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 30× in last 7d / 30× 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-08-21 06:51 UTCGHSA enrichment
  2. 2026-08-21 02:46 UTCEG score recompute
  3. 2026-08-21 02:46 UTCGHSA enrichment
  4. 2026-08-20 22:56 UTCEPSS rescore
  5. 2026-08-20 22:43 UTCGHSA enrichment
  6. 2026-08-20 18:40 UTCGHSA enrichment
  7. 2026-08-20 14:37 UTCGHSA enrichment
  8. 2026-08-20 10:34 UTCGHSA enrichment
  9. 2026-08-20 06:30 UTCGHSA enrichment
  10. 2026-08-20 02:27 UTCGHSA enrichment
  11. 2026-08-19 22:24 UTCGHSA enrichment
  12. 2026-08-19 18:20 UTCEG score recompute
  13. 2026-08-19 18:20 UTCGHSA enrichment
  14. 2026-08-19 17:04 UTCEPSS rescore
  15. 2026-08-19 13:15 UTCGHSA enrichment
  16. 2026-08-19 09:12 UTCGHSA enrichment
  17. 2026-08-19 05:08 UTCGHSA enrichment
  18. 2026-08-19 01:05 UTCGHSA enrichment
  19. 2026-08-18 21:02 UTCGHSA enrichment
  20. 2026-08-18 16:59 UTCEG score recompute
  21. 2026-08-18 16:59 UTCGHSA enrichment
  22. 2026-08-18 13:48 UTCEPSS rescore
  23. 2026-08-18 12:37 UTCEG score recompute
  24. 2026-08-18 12:37 UTCGHSA enrichment
  25. 2026-08-18 12:15 UTCEG score recompute▲ 9.80
Show 5 more
  1. 2026-08-18 12:15 UTCGHSA enrichment
  2. 2026-08-18 12:14 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  3. 2026-08-17 23:21 UTCNVD update
  4. 2026-08-17 22:44 UTCEG score recompute
  5. 2026-08-17 22:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-67919?
CVE-2026-67919 is a critical vulnerability published on August 17, 2026. An issue in Halo 2.25.4 allows a remote attacker to execute arbitrary code via the PluginEndpoint.java, installFromUri method, and DefaultPluginApplicationContextFactory components
When was CVE-2026-67919 disclosed?
CVE-2026-67919 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-67919 actively exploited?
CVE-2026-67919 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 49.6% of all scored CVEs.
What is the CVSS score of CVE-2026-67919?
CVE-2026-67919 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-67919?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-67919, 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-67919

Explore →

Is Your Infrastructure Affected by CVE-2026-67919?

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

Start Free Scan →Browse All CVEs