# CVE-2026-107279: AsyncHttpClient: Digest mutual authentication is switched off by a peer offering qop=auth-int

> Attackers can bypass Digest mutual authentication in AsyncHttpClient by offering qop=auth-int, allowing impersonation of the server.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-qhv6-3pmh-95q4, UBUNTU-CVE-2026-107279

## What is CVE-2026-107279?

CVE-2026-107279 is a high-severity authentication bypass vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. In 3.0.12, a peer offering only Digest qop=auth-int causes mutual-authentication verification to be skipped. AuthenticatorUtils.computeExpectedRspAuth returns no expected value for auth-int, and Interceptors treats that result as unverifiable but nonfatal, so a response with an invalid rspauth value is accepted. A peer that does not know the shared secret can therefore be accepted as the authenticated server. This issue is fixed in version 3.0.13.

Weakness: CWE-757 (Selection of Less-Secure Algorithm During Negotiation), CWE-303 (Incorrect Implementation of Authentication Algorithm)

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


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

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

## Is CVE-2026-107279 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107279 is a high-severity authentication bypass vulnerability in AsyncHttpClient async-http-client, published on 7 Oct 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-107279 in the wild and no public exploit code.

Affected product: AsyncHttpClient async-http-client. 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-107279/ (Markdown: https://insights.sbomify.com/CVE-2026-107279/index.md)
```

## Sources

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

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