Skip to main content
VulnerabilityPublished Updated

CVE-2024-57626: MonetDB · SQL Injection

Affects MonetDBSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 11:42 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Jan 2025

  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

Affected software

ProductAffectedFixed in
GitHubmonetdb/MonetDBpkg:github/monetdb/MonetDBOther threatsAffected
  • =11.49.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

  1. Restrict network access to MonetDB Server instances by implementing strict firewall rules and network segmentation to limit exposure to trusted hosts only.
  2. Monitor database logs and network traffic for unusual or malformed SQL queries targeting join operations, which may indicate exploitation attempts.
  3. Employ Web Application Firewalls (WAFs) or database activity monitoring tools capable of detecting and blocking suspicious SQL commands.
  4. Disable or limit remote access to the database server where possible, enforcing VPN or secure tunnels for administrative access.
  5. Stay informed on official MonetDB security advisories and apply patches promptly once released.
  6. Consider deploying rate limiting or query throttling mechanisms to reduce the risk of DoS from repeated malicious queries.
  7. Conduct regular backups and have a recovery plan to minimize downtime impact in case of successful exploitation.
  8. Engage with MonetDB community or vendor support channels to obtain early warnings and mitigation guidance.

Description

An issue in the mat_join2 component of MonetDB Server v11.49.1 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.

References

Community reviews

Loading reviews…