Skip to main content
VulnerabilityPublished Updated

CVE-2026-79536: bytebase dbhub · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

Until a fix is available, users should consider restricting access to the vulnerable component and monitor for suspicious activity related to SQL injection attempts.

Description

A SQL injection vulnerability exists in bytebase dbhub v1.2.0 within the /utils/sql-parser.ts component. This flaw allows attackers to execute crafted SQL statements that can access sensitive database information. The vulnerability has a critical severity with a CVSS score of 9.1.

References

Community reviews

Loading reviews…