# CVE-2026-87743: Quarkus-vertx-http: authorization bypass via path normalization discrepancy in quarkus http security

> An unauthenticated attacker can bypass authorization checks via path normalization discrepancies to access protected endpoints and sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-pw2v-hfg7-72m6

## What is CVE-2026-87743?

CVE-2026-87743 is a high-severity authentication bypass vulnerability in Red Hat Exploit Intelligence, published on 18 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in Quarkus HTTP security. An unauthenticated attacker can exploit a discrepancy in how paths are normalized between the security matcher and HTTP request dispatchers. This allows the attacker to craft a URL that the security matcher considers public, but which is then routed to a protected endpoint, leading to an authorization bypass and potential unauthorized access to sensitive information.

Weakness: CWE-551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization)

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


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

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

## Is CVE-2026-87743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-87743 is a high-severity authentication bypass vulnerability in Red Hat Exploit Intelligence, published on 18 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-87743 in the wild and no public exploit code.

Affected product: Red Hat Exploit Intelligence. 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-87743/ (Markdown: https://insights.sbomify.com/CVE-2026-87743/index.md)
```

## Sources

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

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