CVE-2026-61620

HoneySQL unchecked entity names can lead to SQL injection results

Published Oct 30, 2026 CVSS 3.1 · 9.8 Critical EPSS < 1% KEV · Not listed
Description
HoneySQL turns Clojure data structures into SQL. From 2.0.0 until 2.7.1392, applications that pass user input or other arbitrary data into the HoneySQL `DSL` by calling `keyword` or `symbol` on that input can produce SQL strings that facilitate SQL injection when executed unchanged by a `JDBC` driver. Some formatters do not apply the existing suspicious-character check to the resulting entity names. The impact depends on the privileges of the database connection executing the generated statement. Input validation before constructing `keyword` or `symbol` entities is a workaround. The maintainer-designated fixed version is 2.7.1392.

Analysis

AI-generated

Technical impact

HoneySQL converts Clojure data structures into SQL strings. From version 2.0.0 through 2.7.1392, if an application passes untrusted user data into the DSL by calling keyword or symbol on that data, the resulting entity names are not always checked for suspicious characters. This flaw allows an attacker to inject arbitrary SQL when the statement is executed by a JDBC driver, potentially compromising any data the database account can access.

Affected Systems

The vulnerability affects the HoneySQL library produced by seancorfield. All projects using HoneySQL versions 2.0.0 up to and including 2.7.1392 are at risk. The fix is available in version 2.7.1392 and later.

Risk and Exploitability

The CVSS score of 9.8 indicates a critical severity. The EPSS score is not available, but the lack of a CISA KEV listing suggests no public exploitation yet. The likely attack vector is via an application that accepts user-supplied data and passes it directly to HoneySQL's keyword or symbol functions without validation. If the database user has high privileges, an attacker may gain full control of the database or exfiltrate sensitive information.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade HoneySQL to version 2.7.1392 or later to apply the official fix.
  • Implement input validation or sanitization before calling keyword or symbol on any external data to prevent malformed entity names.
  • Review application code to ensure that no unsanitized user input is directed to HoneySQL’s DSL functions.

Generated by OpenCVE AI on October 30, 2026 at 21:44 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Seancorfield
Seancorfield honeysql
Vendors & Products Seancorfield
Seancorfield honeysql
Type Values Removed Values Added
Description HoneySQL turns Clojure data structures into SQL. From 2.0.0 until 2.7.1392, applications that pass user input or other arbitrary data into the HoneySQL `DSL` by calling `keyword` or `symbol` on that input can produce SQL strings that facilitate SQL injection when executed unchanged by a `JDBC` driver. Some formatters do not apply the existing suspicious-character check to the resulting entity names. The impact depends on the privileges of the database connection executing the generated statement. Input validation before constructing `keyword` or `symbol` entities is a workaround. The maintainer-designated fixed version is 2.7.1392.
Title HoneySQL unchecked entity names can lead to SQL injection results
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 9.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 30, 2026, 10:14 PM
Reserved
Jul 10, 2026, 5:36 PM
Status
Awaiting Analysis
Published
Oct 30, 2026, 8:17 PM
Modified
Nov 2, 2026, 7:14 PM