# CVE-2026-112017: JeecgBoot before 3.9.5 SQL Injection via SqlInjectionUtil Newline Bypass

> Authenticated attackers can bypass SQL injection filters using newline characters to extract sensitive database contents, including administrator password hashes.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-j5cg-5m27-jqf8

## What is CVE-2026-112017?

CVE-2026-112017 is a high-severity SQL injection vulnerability in JeecgBoot, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JeecgBoot before 3.9.5 contains an sql injection vulnerability that allows authenticated attackers to bypass the SqlInjectionUtil keyword blocklist by inserting newline characters into dictionary and online report SQL fragments. Attackers can send newline-separated payloads to endpoints like /sys/dict/getDictItems for boolean or time-based blind injection, extracting database contents including administrator password hashes from sys_user.

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

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


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

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

## Is CVE-2026-112017 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112017 is a high-severity SQL injection vulnerability in JeecgBoot, published on 18 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-112017 in the wild and no public exploit code.

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

## Sources

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

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