CVE-2026-19360

MEDIUMPre-NVD 4.74.7—
EchelonGraph scoreHIGH confidence

Score 4.7 from GitHub Security Advisory published 2026-08-09. a secondary CVSS source baseline 4.7; sources differ by 0.0.

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

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

A vulnerability was detected in wongcyrus ExcelLexBot up to 0.0.3. This affects the function ExcelLexBotS3TriggerFunction of the component Lambda Function Handler. Performing a manipulation results in improper privilege management. The attack may be initiated remotely. The vendor was contacted early about this disclosure but did not respond in any way. This vulnerability only affects products that are no longer supported by the maintainer.

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

Published

August 9, 2026

Last Modified

August 12, 2026

References (4)

Vendor Advisories for CVE-2026-19360(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 18× 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-08-21 08:56 UTCGHSA enrichment
  2. 2026-08-20 07:27 UTCEG score recompute
  3. 2026-08-20 07:27 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 05:58 UTCEG score recompute
  6. 2026-08-19 05:58 UTCGHSA enrichment
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-18 04:26 UTCEG score recompute
  9. 2026-08-18 04:26 UTCGHSA enrichment
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-17 02:58 UTCEG score recompute
  12. 2026-08-17 02:58 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-16 01:30 UTCEG score recompute
  16. 2026-08-16 01:30 UTCGHSA enrichment
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-15 00:01 UTCGHSA enrichment
  19. 2026-08-13 22:32 UTCEG score recompute
  20. 2026-08-13 22:32 UTCGHSA enrichment
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 21:03 UTCGHSA enrichment
  23. 2026-08-12 17:27 UTCEG score recompute
  24. 2026-08-12 17:27 UTCGHSA enrichment
  25. 2026-08-12 13:50 UTCEPSS rescore
Show 10 more
  1. 2026-08-11 15:58 UTCEG score recompute
  2. 2026-08-11 15:58 UTCGHSA enrichment
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 14:30 UTCEG score recompute
  6. 2026-08-10 14:30 UTCGHSA enrichment
  7. 2026-08-10 14:06 UTCEG score recompute
  8. 2026-08-10 14:06 UTCGHSA enrichment
  9. 2026-08-09 17:16 UTCEG score recompute
  10. 2026-08-09 17:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19360?
CVE-2026-19360 is a medium vulnerability published on August 9, 2026. A vulnerability was detected in wongcyrus ExcelLexBot up to 0.0.3. This affects the function ExcelLexBotS3TriggerFunction of the component Lambda Function Handler. Performing a manipulation results in improper privilege management. The attack may be initiated remotely. The vendor was contacted…
When was CVE-2026-19360 disclosed?
CVE-2026-19360 was first published in the National Vulnerability Database on August 9, 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-19360 actively exploited?
CVE-2026-19360 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 87.4% of all scored CVEs.
What is the CVSS score of CVE-2026-19360?
CVE-2026-19360 has a CVSS v3 base score of 4.7 (NVD).
How do I remediate CVE-2026-19360?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19360, 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-19360

Explore →

Is Your Infrastructure Affected by CVE-2026-19360?

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

Start Free Scan →Browse All CVEs