Skip to main content
CVE-2026-38626VulnerabilityPublished 09/10/2026Updated 09/14/2026

CVE-2026-38626: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 10/25/2026, 16:58:55 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% 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:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubgaurishbahurupi/SQLI-in-Garlic-Hubpkg:github/gaurishbahurupi/SQLI-in-Garlic-HubOther threatsAffected
  • =1.0.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, users should consider applying input validation controls or other protective measures to mitigate SQL injection risks.

Description

Garlic-Hub v1.0.1 is vulnerable to SQL Injection in src/Modules/Items/Repositories/ItemsRepository.php.

Impact

Successful exploitation of this vulnerability could allow attackers to read, modify, or delete sensitive data in the Garlic-Hub database, potentially leading to data breaches, unauthorized data manipulation, or denial of service conditions.

Summary

CVE-2026-38626 identifies a SQL Injection vulnerability in Garlic-Hub v1.0.1 specifically within the ItemsRepository.php source file. The vulnerability permits unauthenticated remote attackers to inject malicious SQL queries due to improper input sanitization or validation. The CVSS 3.1 base score is 9.8, indicating critical severity with network attack vector, low attack complexity, no privileges or user interaction required, and full impact on confidentiality, integrity, and availability.

Weaknesses

References

Community reviews

Loading reviews…