# CVE-2026-110733: Apache SIS: SQL injection via unvalidated ORDER BY sort expression in the SQL feature store


- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-643p-v8jr-8f24

## What is CVE-2026-110733?

CVE-2026-110733 is a medium-severity vulnerability in Apache SIS, published on 26 Oct 2026. 

### Official description

Vulnerability in the SQL storage module of Apache SIS. When sorting a stream of features, the clause is copied after ORDER BY without quoting the identifier character. A crafter sort clause could inject SQL in the query.

This issue affects the sql-storage module of Apache SIS from version 1.0 through 1.6 inclusive. Other modules such as sis-referencing are not impacted. Users are recommended to upgrade to version 1.7, which fixes the issue.

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

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


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

No fix has been published for CVE-2026-110733 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-110733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110733 is a medium-severity vulnerability in Apache SIS, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110733 in the wild and no public exploit code.

Affected product: Apache SIS. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-110733/ (Markdown: https://insights.sbomify.com/CVE-2026-110733/index.md)
```

## Sources

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

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