Quick answers
- Is CVE-2026-102740 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-102740 being exploited in the wild.
- How severe is CVE-2026-102740?
- Medium severity, with a CVSS score of 5.8, published 15 October 2026.
- Which products and versions are affected?
- AsyncHttpClient 2.0.0 to 2.16.0 and 3.0.0 to 3.0.11.
- Is there a fix for CVE-2026-102740?
- Yes: fixed in 2.16.1 and 3.0.12. Until then: Do not use ResumableAsyncHandler to decorate another AsyncHandler; use the no-argument constructor instead to employ the no-op processor which is unaffected by this vulnerability. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-102740 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-102740?
- Check whether you run AsyncHttpClient at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.16.1 and 3.0.12
Do not use ResumableAsyncHandler to decorate another AsyncHandler; use the no-argument constructor instead to employ the no-op processor which is unaffected by this vulnerability.
Technical details
PropertiesBasedResumableProcessor stores resumable download state at a predictable path ($java.io.tmpdir/ahc/ResumableAsyncHandler.properties) with default permissions, making it readable by other local users and exploitable via symlink attacks. The vulnerability requires local file system access and affects applications that use ResumableAsyncHandler to decorate another AsyncHandler. The no-argument constructors use a no-op processor and are unaffected.
Affected products
- AsyncHttpClient AsyncHttpClient 2.0.0 to 2.16.0 and 3.0.0 to 3.0.11
Timeline
- 2026-10-15: disclosed: CVE-2026-102740 published
- 2026-08-05: patched: Fix committed hardening symlink and permission behavior