CVE-2026-19245

LOWPre-NVD 3.33.3—
EchelonGraph scoreHIGH confidence

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-08-07. a secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
3.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.3Exploit: Elevated riskExposed: 0

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

A flaw has been found in HKUDS nanobot up to 0.2.1. The impacted element is the function ExecTool._prepare_command of the file nanobot/agent/tools/shell.py of the component Login-shell Environment Handler. Executing a manipulation can lead to information disclosure. The attack requires local access. The exploit has been published and may be used. Upgrading to version 0.3.0 is sufficient to resolve this issue. This patch is called 4525. The affected component should be upgraded. Multiple issues were reported to the project. They reacted with a high level of professionalism and kindness: "The report concerns shell startup files reintroducing environment variables when command execution defaults to a login shell. The default was changed so exec does not use a login shell unless explicitly requested".

CVSS v3
3.3
EG Score
3.3(high)
EG Risk
31(Track)
EG Risk 31/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
Severity33% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 12, 2026

References (9)

Vendor Advisories for CVE-2026-19245(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 32× 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 02:02 UTCEG score recompute
  2. 2026-08-21 02:02 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-18 08:24 UTCEG score recompute
  7. 2026-08-18 08:23 UTCGHSA enrichment
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 02:14 UTCEPSS rescore
  11. 2026-08-15 14:42 UTCEG score recompute
  12. 2026-08-15 14:42 UTCGHSA enrichment
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 21:04 UTCEG score recompute
  16. 2026-08-12 21:04 UTCGHSA enrichment
  17. 2026-08-12 13:50 UTCEPSS rescore
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 14:30 UTCEG score recompute
  21. 2026-08-10 14:30 UTCGHSA enrichment
  22. 2026-08-10 14:28 UTCNVD updateCVSS v4 → 1.9
  23. 2026-08-10 13:37 UTCEG score recompute
  24. 2026-08-10 13:37 UTCGHSA enrichment
  25. 2026-08-10 13:36 UTCMITRE cvelistV5CVSS v4 → 4.8
Show 7 more
  1. 2026-08-09 13:46 UTCEPSS rescore
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 21:32 UTCEG score recompute
  4. 2026-08-07 21:32 UTCGHSA enrichment
  5. 2026-08-07 21:31 UTCNVD updateCVSS v4 → 1.9
  6. 2026-08-07 21:02 UTCEG score recompute
  7. 2026-08-07 21:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-19245?
CVE-2026-19245 is a low vulnerability published on August 7, 2026. A flaw has been found in HKUDS nanobot up to 0.2.1. The impacted element is the function ExecTool.preparecommand of the file nanobot/agent/tools/shell.py of the component Login-shell Environment Handler. Executing a manipulation can lead to information disclosure. The attack requires local access.…
When was CVE-2026-19245 disclosed?
CVE-2026-19245 was first published in the National Vulnerability Database on August 7, 2026, with the most recent update on August 12, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19245 actively exploited?
CVE-2026-19245 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.7% of all scored CVEs.
What is the CVSS score of CVE-2026-19245?
CVE-2026-19245 has a CVSS v3 base score of 3.3 (NVD).
How do I remediate CVE-2026-19245?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19245, 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-19245

Explore →

Is Your Infrastructure Affected by CVE-2026-19245?

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

Start Free Scan →Browse All CVEs