CVE-2026-19636

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

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

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

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

An issue was identified in which CSRF tokens were generated using a predictable method, potentially reducing their effectiveness as a security control. This has been addressed by improving the randomness and entropy of token generation.

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

Published

August 14, 2026

Last Modified

August 19, 2026

Advisory Details (1)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

[R1] Security Center Version 6.9.0 Fixes Multiple Vulnerabilities - Security Advisory | Tenable®

https://www.tenable.com/security/tns-2026-22

Vendor Advisories for CVE-2026-19636(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 22× in last 7d / 22× 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-20 15:13 UTCGHSA enrichment
  2. 2026-08-19 17:24 UTCEG score recompute
  3. 2026-08-19 17:24 UTCGHSA enrichment
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-19 13:07 UTCGHSA enrichment
  6. 2026-08-18 15:18 UTCEG score recompute
  7. 2026-08-18 15:18 UTCGHSA enrichment
  8. 2026-08-18 13:48 UTCEPSS rescore
  9. 2026-08-18 09:53 UTCEG score recompute
  10. 2026-08-18 09:52 UTCGHSA enrichment
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 12:02 UTCEG score recompute
  13. 2026-08-17 12:02 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 14:13 UTCEG score recompute
  16. 2026-08-16 14:13 UTCGHSA enrichment
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 16:24 UTCGHSA enrichment
  19. 2026-08-14 18:35 UTCEG score recompute
  20. 2026-08-14 18:35 UTCGHSA enrichment
  21. 2026-08-14 17:30 UTCEG score recompute
  22. 2026-08-14 17:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-19636?
CVE-2026-19636 is a medium vulnerability published on August 14, 2026. An issue was identified in which CSRF tokens were generated using a predictable method, potentially reducing their effectiveness as a security control. This has been addressed by improving the randomness and entropy of token generation.
When was CVE-2026-19636 disclosed?
CVE-2026-19636 was first published in the National Vulnerability Database on August 14, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-19636 actively exploited?
CVE-2026-19636 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 82.4% of all scored CVEs.
What is the CVSS score of CVE-2026-19636?
CVE-2026-19636 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-19636?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-19636, 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-19636

Explore →

Is Your Infrastructure Affected by CVE-2026-19636?

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

Start Free Scan →Browse All CVEs