# CVE-2026-77874: IBM Enterprise Build of Quarkus is affected by multiple vulnerabilities

> Remote unauthenticated attackers can execute SQL injection to view, add, modify, or delete backend database information in IBM Enterprise Build of Quarkus.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-hcr5-gpj4-pqhc

## What is CVE-2026-77874?

CVE-2026-77874 is a high-severity SQL injection vulnerability in IBM Enterprise Build of Quarkus, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

IBM Enterprise Build of Quarkus 3.27.1 through 3.27.5.SP1, and 3.33.1 through 3.33.3.SP1 is vulnerable to SQL injection. A remote unauthenticated attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.

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

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


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

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

## Is CVE-2026-77874 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-77874 is a high-severity SQL injection vulnerability in IBM Enterprise Build of Quarkus, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-77874 in the wild and no public exploit code.

Affected product: IBM Enterprise Build of Quarkus. 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-77874/ (Markdown: https://insights.sbomify.com/CVE-2026-77874/index.md)
```

## Sources

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

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