PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-107375 jhipster CVE debrief

A CVE debrief for CVE-2026-107375, a SQL injection vulnerability in JHipster-generated reactive applications. The vulnerability occurs in the paginated entity list endpoints, where the `sort` request parameter is taken verbatim from the user and concatenated into the SQL `ORDER BY` clause without quoting or validation. This allows an authenticated low-privileged user to execute arbitrary SQL, leading to full C/I/A impact. Defenders should assess exposure, verify JHipster versions, and implement input validation and quoting for SQL queries.

Vendor
jhipster
Product
generator-jhipster
CVSS
HIGH 8.8
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-08
Original CVE updated
2026-10-08
Advisory published
2026-10-08
Advisory updated
2026-10-08

Who should care

Developers and administrators of JHipster-generated reactive applications should assess their exposure and take necessary actions to mitigate the vulnerability. They should verify JHipster versions, implement input validation and quoting for SQL queries, and monitor for suspicious database activity.

Why it matters

CVE-2026-107375 is a high-severity SQL injection vulnerability in JHipster-generated reactive applications. An authenticated low-privileged user can execute arbitrary SQL, leading to full C/I/A impact. Defenders should assess exposure, verify JHipster versions, and implement input validation and quoting for SQL queries.

  • An authenticated low-privileged user can execute arbitrary SQL, read any table, modify or delete data, and drop tables.
  • The vulnerability allows for full C/I/A impact.
  • Defenders should verify JHipster versions and implement input validation and quoting for SQL queries.
  • Monitoring for suspicious database activity is recommended.

Technical summary

The CVE-2026-107375 vulnerability is an SQL injection issue in JHipster-generated reactive applications. The vulnerability occurs in the paginated entity list endpoints, where the `sort` request parameter is taken verbatim from the user and concatenated into the SQL `ORDER BY` clause without quoting or validation. This allows an authenticated low-privileged user to execute arbitrary SQL, leading to full C/I/A impact. Defenders should assess exposure, verify JHipster versions, and implement input validation and quoting for SQL queries.

Defensive priority

High

Recommended defensive actions

  • Review and update JHipster versions to 9.4.0 or later
  • Implement input validation and quoting for SQL queries
  • Monitor for suspicious database activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • 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 item provide details on the SQL injection vulnerability in JHipster-generated reactive applications. The vulnerability allows an authenticated low-privileged user to execute arbitrary SQL, read any table, modify or delete data, and drop tables. The evidence is based on the official CVE Program record and the source item details.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-107375 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-107375

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-107375 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-107375

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental 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.