Red Hat JBoss Enterprise Application Platform…: Improper Neutralization of Special Elements used in an SQL Command
CVE-2026-0603 is a high-severity improper neutralization of special elements used in an SQL command vulnerability in Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 from Red Hat, with a CVSS 3.1 base score of 8.3 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 1.03% chance of exploitation within 30 days, higher than 64% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7 you run against the affected versions below, and install the vendor's latest release.
Affected products and versions
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- LowPerformance or availability is reduced.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L. Scored by CNA (redhat.com).
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.3 | High | CNA (redhat.com) |
| CVSS 3.1 | 8.3 | High | CNA |
Official description
A flaw was found in Hibernate. A remote attacker with low privileges could exploit a second-order SQL injection vulnerability by providing specially crafted, unsanitized non-alphanumeric characters in the ID column when the InlineIdsOrClauseBuilder is used. This could lead to sensitive information disclosure, such as reading system files, and allow for data manipulation or deletion within the application's database, resulting in an application level denial of service.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an SQL Command
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
More Improper Neutralization of Special Elements used in an SQL Command vulnerabilities (CWE-89)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other references
- access.redhat.com/errata/RHSA-2026:4915
- access.redhat.com/errata/RHSA-2026:4916
- access.redhat.com/errata/RHSA-2026:4917
- access.redhat.com/errata/RHSA-2026:4924
- access.redhat.com/errata/RHSA-2026:6011
- access.redhat.com/errata/RHSA-2026:6012
- access.redhat.com/errata/RHSA-2026:76128
- access.redhat.com/errata/RHSA-2026:76129
- access.redhat.com/errata/RHSA-2026:76130
- access.redhat.com/errata/RHSA-2026:76132
- access.redhat.com/errata/RHSA-2026:76134
- access.redhat.com/security/cve/CVE-2026-0603
- bugzilla.redhat.com/show_bug.cgi?id=2427147
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-0603.json
Other vulnerabilities in Red Hat JBoss Enterprise Application Platform 7.1 EUS for RHEL 7
- 9.6 Critical severity
- 7.5 High severity
- 7.5 High severity
- 7.3 High severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Neutralization of Special Elements used in an SQL Command vulnerabilities
- 9.4 Critical severity
- 7.6 High severity
- 8.5 High severity
- 8.5 High severity
- 7.6 High severity
- 8.5 High severity
Spotted an error? Tell us.