CVE-1999-0710

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 11.6% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 12%CVSS v2: 7.5Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

A fix is available — apply it.

The Squid package in Red Hat Linux 5.2 and 6.0, and other distributions, installs cachemgr.cgi in a public web directory, which allows remote attackers to use it as an intermediary to connect to other systems.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
64(Track)
EG Risk 64/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
12%
EPSS %ILE
96%
KEV
Not listed

Published

July 25, 1999

Last Modified

June 16, 2026

References (16)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatsquid-7:2.5.STABLE6-3.4E.92005-06-14redhat
redhatpatch2005-06-13redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
squid—2.5.7-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
squid—2.5.7-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
squid—2.5.7-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
squid—2.5.7-1—
Debian:3.0(1)
PackageVulnerable rangeFixed inDependents
squid—2.4.6-2woody4—

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 0× in last 7d / 3× 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-09-16 12:20 UTCOSV refresh
  2. 2026-09-04 04:59 UTCEPSS rescore
  3. 2026-08-28 11:53 UTCOSV refresh
  4. 2026-08-12 00:14 UTCOSV refresh
  5. 2026-07-27 00:09 UTCOSV refresh
  6. 2026-07-26 13:19 UTCEG score recompute▲ 7.50
  7. 2026-07-23 00:41 UTCEG score recompute
  8. 2026-07-23 00:23 UTCEG score recompute
  9. 2026-07-22 23:45 UTCEG score recompute
  10. 2026-07-22 21:25 UTCEG score recompute
  11. 2026-07-20 17:02 UTCEPSS rescore
  12. 2026-07-18 09:59 UTCEPSS rescore
  13. 2026-07-16 16:58 UTCEPSS rescore
  14. 2026-07-15 16:53 UTCEPSS rescore
  15. 2026-07-15 01:55 UTCEPSS rescore
  16. 2026-07-11 08:22 UTCEPSS rescore
  17. 2026-07-09 18:45 UTCOSV refresh
  18. 2026-07-08 15:08 UTCEPSS rescore
  19. 2026-07-04 06:26 UTCEPSS rescore
  20. 2026-07-02 14:00 UTCEPSS rescore
  21. 2026-06-29 14:02 UTCEPSS rescore
  22. 2026-06-28 14:02 UTCEPSS rescore
  23. 2026-06-27 03:04 UTCEPSS rescore
  24. 2026-06-24 14:01 UTCEPSS rescore
  25. 2026-06-23 21:29 UTCEPSS rescore
Show 46 more
  1. 2026-06-22 14:22 UTCEPSS rescore
  2. 2026-06-21 04:59 UTCOSV refresh
  3. 2026-06-21 01:56 UTCEPSS rescore
  4. 2026-06-18 17:49 UTCEPSS rescore
  5. 2026-06-18 17:49 UTCEPSS rescore
  6. 2026-06-17 17:49 UTCEPSS rescore
  7. 2026-06-16 17:49 UTCEPSS rescore
  8. 2026-06-14 23:13 UTCEPSS rescore
  9. 2026-06-13 22:56 UTCEPSS rescore
  10. 2026-06-12 23:07 UTCEPSS rescore
  11. 2026-06-11 13:55 UTCEPSS rescore
  12. 2026-06-10 22:13 UTCEPSS rescore
  13. 2026-06-10 13:17 UTCEPSS rescore
  14. 2026-06-07 15:21 UTCEPSS rescore
  15. 2026-06-06 13:44 UTCEPSS rescore
  16. 2026-06-05 06:07 UTCEPSS rescore
  17. 2026-06-04 13:09 UTCEPSS rescore
  18. 2026-06-02 20:10 UTCEPSS rescore
  19. 2026-06-01 13:48 UTCEPSS rescore
  20. 2026-05-31 22:27 UTCEPSS rescore
  21. 2026-05-31 22:23 UTCEG score recompute
  22. 2026-05-31 22:23 UTCVendor advisory
  23. 2026-05-31 22:23 UTCGHSA enrichment
  24. 2026-05-31 00:13 UTCEPSS rescore
  25. 2026-05-31 00:13 UTCEPSS rescore
  26. 2026-05-29 13:40 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-28 13:42 UTCEPSS rescore
  31. 2026-05-27 13:37 UTCEPSS rescore
  32. 2026-05-27 13:37 UTCEPSS rescore
  33. 2026-05-26 13:41 UTCEPSS rescore
  34. 2026-05-26 13:41 UTCEPSS rescore
  35. 2026-05-26 13:41 UTCEPSS rescore
  36. 2026-05-26 07:16 UTCEPSS rescore
  37. 2026-05-26 07:16 UTCEPSS rescore
  38. 2026-05-24 16:42 UTCEPSS rescore
  39. 2026-05-22 23:41 UTCOSV refresh
  40. 2026-05-22 21:15 UTCEPSS rescore
  41. 2026-05-21 22:38 UTCEPSS rescore
  42. 2026-05-20 22:36 UTCEPSS rescore
  43. 2026-05-20 11:20 UTCEPSS rescore
  44. 2026-05-20 11:20 UTCEPSS rescore
  45. 2026-05-18 21:29 UTCEPSS rescore
  46. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-20465✓ verified
    First seen Jul 23, 1999

    Squid Web Proxy 2.2 - 'cachemgr.cgi' Unauthorized Connection

    Open source ↗

Related CVEs(same product + same vendor)

Frequently asked(4)

What is CVE-1999-0710?
CVE-1999-0710 is a high vulnerability published on July 25, 1999. The Squid package in Red Hat Linux 5.2 and 6.0, and other distributions, installs cachemgr.cgi in a public web directory, which allows remote attackers to use it as an intermediary to connect to other systems.
When was CVE-1999-0710 disclosed?
CVE-1999-0710 was first published in the National Vulnerability Database on July 25, 1999, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-1999-0710 actively exploited?
CVE-1999-0710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12% probability of exploitation in the next 30 days, which ranks it in the top 4.1% of all scored CVEs.
How do I remediate CVE-1999-0710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-1999-0710, 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-1999-0710

Explore →

Is Your Infrastructure Affected by CVE-1999-0710?

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

Book a Demo →Browse All CVEs