Unauthenticated remote SQL injection in a widely used enterprise Java framework distribution (IBM Quarkus) can expose or modify backend databases across many apps.
CVE-2026-77874
Remote SQL injection in IBM Enterprise Build of Quarkus allowing unauthenticated DB access.
Is CVE-2026-77874 being exploited?
Not confirmed. CVE-2026-77874 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-77874?
CVE-2026-77874 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-77874?
Not known from our data. No patch reference has been recorded for CVE-2026-77874, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-77874 affect?
CVE-2026-77874 affects IBM Enterprise Build of Quarkus 3.27.1–3.27.5.SP1, IBM Enterprise Build of Quarkus 3.33.1–3.33.3.SP1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-77874?
Apply vendor fixes/mitigations ASAP; sanitize inputs, block/inspect suspicious requests, review logs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote unauthenticated SQL injection allows attackers to read, add, modify, or delete backend database data.
Immediate action required
- affected>= 3.27.1 and <= 3.27.5.SP1
- affected>= 3.33.1 and <= 3.33.3.SP1
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- yes
- technical impact
- partial
Assessed by CISA 24 Sept 2026 (SSVC 2.0.3).
timeline
- 24 Sept 2026Published
- 24 Sept 2026CISA SSVC assessment: exploitation none · same day later
- 24 Sept 2026CVE record last updated · same day later
- 25 Sept 2026Analysed by vulneraibility.com · 1 day later
- Patchibm.com /support/pages/node/7289050
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.