# CVE-2026-121007: SQL::Abstract versions from 1.90_01 before 2.000001_04 for Perl allow SQL injection via the where values of a nested statement in an identifier position.


- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** ALPINE-CVE-2026-121007, DEBIAN-CVE-2026-121007, GHSA-24q3-fp2q-x646, UBUNTU-CVE-2026-121007

## What is CVE-2026-121007?

CVE-2026-121007 is a high-severity vulnerability, published on 4 Nov 2026. 

### Official description

SQL::Abstract versions from 1.90_01 before 2.000001_04 for Perl allow SQL injection via the where values of a nested statement in an identifier position.

A nested statement such as { -select => ... } in a position where plain scalars are identifiers treats its own plain scalars as identifiers too. These positions are the select list, ORDER BY, GROUP BY, RETURNING, and with the ExtraClauses plugin FROM (-as) and JOIN (to). The values of the statement's where, having and set clauses, and the rows of a -values, go into the SQL text instead of the bind list, unescaped unless quote_char is set. Subselects in a WHERE condition are not affected.

An application that passes untrusted input as a where value of such a nested statement, expecting it to be bound, allows SQL injection.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-121007?


## How do I fix CVE-2026-121007?

Upgrade to a fixed version.

## Is CVE-2026-121007 being exploited?

There is no known exploitation of CVE-2026-121007 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121007 and fix it if it is affected.

What it is: CVE-2026-121007 is a high-severity vulnerability, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121007 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121007/ (Markdown: https://insights.sbomify.com/CVE-2026-121007/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121007
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121007
- OSV: https://osv.dev/vulnerability/CVE-2026-121007

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121007/
Summaries are generated and may contain mistakes; the official description above is the record.
