CVE-2026-13512

MEDIUMPre-NVD 6.36.3—
EchelonGraph scoreMEDIUM confidence

Score 6.3 from GitHub Security Advisory (severity: LOW) published 2026-06-29. A secondary CVSS source baseline 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.3Exploit: None knownExposed services: Not assessed

An upstream fix is merged but not yet released — mitigate (WAF / firewall / segmentation) until the release ships, then apply it.

A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::state_key of the file src/query/service/src/servers/http/v1/session/client_session_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is possible to initiate the attack remotely. The exploit is publicly available and might be used. The pull request to fix this issue awaits acceptance.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100

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 (value × EchelonGraph’s weight)
Severity63% × 45%
The EG Score, 6.3 of 10.
Exploitation0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.
EPSS PROB
0.4%
EPSS %ILE
30th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

An upstream fix is merged but not yet in a tagged release. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines until it ships, then apply the release.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact partial (CVSS v4.0 confidentiality and integrity impact neither High). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 28, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
github_pr

fix(query): scope HTTP session state by tenant

Fix merged in databendlabs/databend PR #19931 on 2026-06-28 — awaiting tagged release

https://github.com/databendlabs/databend/pull/19931
generic

bug: Databend HTTP Client Session State Key Collision · Issue #19930 · databendlabs/databend · GitHub

https://github.com/databendlabs/databend/issues/19930

Vendor Advisories for CVE-2026-13512(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 10× in last 7d / 29× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 183 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 18:23 UTCEG score recompute
  2. 2026-10-11 14:57 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  4. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  6. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  7. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  8. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  10. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  11. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  13. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  14. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  16. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.4% · 29th percentile
  17. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  18. 2026-09-23 07:37 UTCEG score recompute
  19. 2026-09-23 07:37 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  21. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  22. 2026-09-18 07:05 UTCEG score recompute
  23. 2026-09-18 07:05 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  24. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 75 more
  1. 2026-09-13 14:21 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  2. 2026-09-12 15:18 UTCEG score recompute
  3. 2026-09-12 15:18 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  4. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-09-11 09:36 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-09-06 14:48 UTCEG score recompute
  11. 2026-09-06 14:48 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  12. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  14. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  16. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-08-30 19:09 UTCEG score recompute
  18. 2026-08-30 19:09 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  19. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-08-27 22:50 UTCEG score recompute
  22. 2026-08-27 22:50 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  23. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-08-24 12:43 UTCEG score recompute
  26. 2026-08-24 12:43 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  27. 2026-08-23 08:31 UTCEG score recompute
  28. 2026-08-23 08:31 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  29. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  30. 2026-08-22 09:13 UTCEG score recompute
  31. 2026-08-22 09:13 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  32. 2026-08-21 23:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  33. 2026-08-21 04:57 UTCEG score recompute
  34. 2026-08-21 04:57 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  35. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  36. 2026-08-20 05:58 UTCEG score recompute
  37. 2026-08-20 05:58 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  38. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  39. 2026-08-18 23:23 UTCEG score recompute
  40. 2026-08-18 23:23 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  41. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  42. 2026-08-17 06:11 UTCEG score recompute
  43. 2026-08-17 06:11 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  44. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  45. 2026-08-16 07:12 UTCEG score recompute
  46. 2026-08-16 07:12 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  47. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  48. 2026-08-15 08:13 UTCEG score recompute
  49. 2026-08-15 08:13 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  50. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  51. 2026-08-14 08:20 UTCEG score recompute
  52. 2026-08-14 08:20 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  53. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  54. 2026-08-13 09:20 UTCEG score recompute
  55. 2026-08-13 09:20 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  56. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  57. 2026-08-12 10:21 UTCEG score recompute
  58. 2026-08-12 10:21 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  59. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  60. 2026-08-11 11:16 UTCEG score recompute
  61. 2026-08-11 11:16 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  62. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  63. 2026-08-10 12:16 UTCEG score recompute
  64. 2026-08-10 12:16 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  65. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  66. 2026-08-09 13:17 UTCEG score recompute
  67. 2026-08-09 13:17 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  68. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  69. 2026-08-08 14:18 UTCEG score recompute
  70. 2026-08-08 14:18 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  71. 2026-08-07 15:18 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  72. 2026-08-06 16:19 UTCEG score recompute
  73. 2026-08-06 16:19 UTCGHSA enrichmentGHSA-m84g-jvj9-9qg6 · GitHub severity LOW · GitHub CVSS 6.3
  74. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.2% · 12th percentile
  75. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.2% · 12th percentile

Frequently asked(5)

What is CVE-2026-13512?
CVE-2026-13512 is a medium-severity vulnerability; its CVE record was published on June 28, 2026. A vulnerability was identified in Databend up to 1.2.881 on HTTP. This affects the function ClientSessionManager::statekey of the file src/query/service/src/servers/http/v1/session/clientsession_manager.rs of the component Tenant Handler. The manipulation leads to authorization bypass. It is…
When was the CVE record for CVE-2026-13512 published?
The CVE record for CVE-2026-13512 was published on June 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of June 30, 2026; the record at its source may have been updated since.
Is CVE-2026-13512 actively exploited?
CVE-2026-13512 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (30th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13512?
CVE-2026-13512 has a CVSS base score of 6.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-13512?
An upstream fix for CVE-2026-13512 has been merged but is not yet in a tagged release. Until it ships, restrict network exposure of the affected system or apply the vendor's mitigation, then update to the release that contains the fix. The vendor advisories EchelonGraph has for CVE-2026-13512 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-13512?

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