CVE-2013-7397

NONECVSS 0.0
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 1%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

Async Http Client (aka AHC or async-http-client) before 1.9.0 skips X.509 certificate verification unless both a keyStore location and a trustStore location are explicitly set, which allows man-in-the-middle attackers to spoof HTTPS servers by presenting an arbitrary certificate during use of a typical AHC configuration, as demonstrated by a configuration that does not send client certificates.

CVSS v3
—
EG Score
0.0(none)
EPSS
58.4%
KEV
Not listed

Published

June 24, 2015

Last Modified

May 6, 2026

References (20)

Vendor Advisories for CVE-2013-7397(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatasync-http-client2015-08-05redhat
redhatpatch2015-06-23redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.ning:async-http-client1.0.0 ... 1.9.0-BETA9 (86 versions)1.9.0—

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:41 UTCEPSS rescore
  2. 2026-07-06 02:20 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-05 02:26 UTCEPSS rescore
  5. 2026-07-04 06:27 UTCEPSS rescore
  6. 2026-07-02 15:21 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-28 14:03 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-28 04:53 UTCEPSS rescore
  11. 2026-06-27 03:05 UTCEPSS rescore
  12. 2026-06-25 13:47 UTCEPSS rescore
  13. 2026-06-25 13:47 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 22:59 UTCOSV refresh
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-23 21:30 UTCEPSS rescore
  19. 2026-06-22 14:22 UTCEPSS rescore
  20. 2026-06-22 14:22 UTCEPSS rescore
  21. 2026-06-21 14:53 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-18 17:49 UTCEPSS rescore
Show 55 more
  1. 2026-06-18 17:49 UTCEPSS rescore
  2. 2026-06-17 17:49 UTCEPSS rescore
  3. 2026-06-17 17:49 UTCEPSS rescore
  4. 2026-06-16 17:49 UTCEPSS rescore
  5. 2026-06-16 17:49 UTCEPSS rescore
  6. 2026-06-16 17:49 UTCEPSS rescore
  7. 2026-06-15 17:44 UTCEPSS rescore
  8. 2026-06-14 23:14 UTCEPSS rescore
  9. 2026-06-13 22:57 UTCEPSS rescore
  10. 2026-06-12 23:08 UTCEPSS rescore
  11. 2026-06-11 13:56 UTCEPSS rescore
  12. 2026-06-10 22:15 UTCEPSS rescore
  13. 2026-06-10 13:18 UTCEPSS rescore
  14. 2026-06-08 14:14 UTCEPSS rescore
  15. 2026-06-07 15:22 UTCEPSS rescore
  16. 2026-06-07 06:23 UTCOSV refresh
  17. 2026-06-06 13:45 UTCEPSS rescore
  18. 2026-06-06 13:45 UTCEPSS rescore
  19. 2026-06-05 22:44 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 06:08 UTCEPSS rescore
  22. 2026-06-05 06:08 UTCEPSS rescore
  23. 2026-06-04 13:09 UTCEPSS rescore
  24. 2026-06-04 13:09 UTCEPSS rescore
  25. 2026-06-02 20:10 UTCEPSS rescore
  26. 2026-06-02 20:10 UTCEPSS rescore
  27. 2026-06-01 13:49 UTCEPSS rescore
  28. 2026-06-01 13:49 UTCEPSS rescore
  29. 2026-05-31 22:28 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 00:14 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-29 13:41 UTCEPSS rescore
  34. 2026-05-29 13:41 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-28 13:42 UTCEPSS rescore
  37. 2026-05-28 13:42 UTCEPSS rescore
  38. 2026-05-27 13:38 UTCEPSS rescore
  39. 2026-05-27 13:38 UTCEPSS rescore
  40. 2026-05-26 13:41 UTCEPSS rescore
  41. 2026-05-26 13:41 UTCEPSS rescore
  42. 2026-05-26 07:16 UTCEPSS rescore
  43. 2026-05-26 07:16 UTCEPSS rescore
  44. 2026-05-23 00:55 UTCEG score recompute
  45. 2026-05-23 00:55 UTCVendor advisory
  46. 2026-05-22 21:15 UTCEPSS rescore
  47. 2026-05-22 21:15 UTCEPSS rescore
  48. 2026-05-22 21:15 UTCEPSS rescore
  49. 2026-05-21 22:39 UTCEPSS rescore
  50. 2026-05-20 22:37 UTCEPSS rescore
  51. 2026-05-20 22:37 UTCEPSS rescore
  52. 2026-05-20 11:21 UTCEPSS rescore
  53. 2026-05-20 11:21 UTCEPSS rescore
  54. 2026-05-18 21:29 UTCEPSS rescore
  55. 2026-05-18 21:29 UTCEPSS rescore

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2013-7397?
CVE-2013-7397 is a none vulnerability published on June 24, 2015. Async Http Client (aka AHC or async-http-client) before 1.9.0 skips X.509 certificate verification unless both a keyStore location and a trustStore location are explicitly set, which allows man-in-the-middle attackers to spoof HTTPS servers by presenting an arbitrary certificate during use of a…
When was CVE-2013-7397 disclosed?
CVE-2013-7397 was first published in the National Vulnerability Database on June 24, 2015, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2013-7397 actively exploited?
CVE-2013-7397 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 58.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2013-7397?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2013-7397, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2013-7397

Explore →

Is Your Infrastructure Affected by CVE-2013-7397?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs