CVE-2026-112017 jeecgboot CVE debrief

Who should care

Defenders responsible for JeecgBoot deployments should assess exposure and prioritize patching or mitigations to prevent exploitation. This includes verifying if the system is using JeecgBoot versions before 3.9.5 and applying patches or mitigations to prevent exploitation. Additionally, defenders should consider implementing additional security controls to prevent SQL injection attacks and monitor for suspicious activity on the /sys/dict/getDictItems and

Why it matters

CVE-2026-112017 is a high-severity SQL injection vulnerability in JeecgBoot versions before 3.9.5, allowing authenticated attackers to bypass the SqlInjectionUtil keyword blocklist and potentially extract sensitive database contents. Defenders should prioritize verifying exposure and applying patches or mitigations to prevent exploitation.

• Potential extraction of sensitive database contents, including administrator password hashes
• Possible disruption of database operations through SQL injection
• Need for verification of exposure and application of patches or mitigations
• Potential impact on system availability and data integrity

Technical summary

The vulnerability exists in the SqlInjectionUtil class, which can be bypassed by inserting newline characters into dictionary and online report SQL fragments. This allows for boolean or time-based blind injection, potentially extracting database contents including administrator password hashes. The vulnerability affects JeecgBoot versions before 3.9.5, and defenders should prioritize verifying exposure and applying patches or mitigations to prevent exploitation. The CVE record and source references provide details on the vulnerability, including its description, CVSS score, and affected versions.

Defensive priority

Defenders should prioritize verifying exposure and applying patches or mitigations, as this vulnerability allows for potential extraction of sensitive database contents.

Recommended defensive actions

• Verify exposure by checking if the system is using JeecgBoot versions before 3.9.5
• Apply patches or mitigations to prevent exploitation
• Monitor for suspicious activity on the /sys/dict/getDictItems endpoint
• Consider implementing additional security controls to prevent SQL injection attacks
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source references provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation beyond patch 3.9.5.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.