# CVE-2026-121008: SQL::Abstract::Tree versions before 2.000001_04 for Perl allow cross-site scripting via unescaped SQL text and bind values in the html profile.


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** ALPINE-CVE-2026-121008, DEBIAN-CVE-2026-121008, GHSA-fcg4-533h-9xx3, UBUNTU-CVE-2026-121008

## What is CVE-2026-121008?

CVE-2026-121008 is a medium-severity vulnerability, published on 4 Nov 2026. 

### Official description

SQL::Abstract::Tree versions before 2.000001_04 for Perl allow cross-site scripting via unescaped SQL text and bind values in the html profile.

The html profile wraps keywords and placeholders in span elements and breaks lines with br elements, so its output is meant to go into a page as is. The format method does not HTML-escape the SQL text or the bind values it fills in around that markup.

An application that renders SQL formatted with the html profile, such as in a debug panel or query log, allows an attacker who controls a bind value or part of the SQL text to embed JavaScript in the page.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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


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

Upgrade to a fixed version.

## Is CVE-2026-121008 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121008 is a medium-severity vulnerability, published on 4 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121008 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-121008/ (Markdown: https://insights.sbomify.com/CVE-2026-121008/index.md)
```

## Sources

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

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