CVE-2026-12490

HIGHNVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

When a provide-xfr is given with a tls-auth-name, a secondary requesting a transfer should provide a client certificate with that name. However, no client certificate is needed when the request comes in over TLS over the regular tls-port (and not the tls-auth-port) or over over TCP over the regular port, when the other conditions of the provide-xfr rule match.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
3.6%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
No patch confirmed yet.
generic
https://www.nlnetlabs.nl/downloads/nsd/CVE-2026-12490.txt

Vendor Advisories for CVE-2026-12490(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntunsd3 (4.1.7-1ubuntu0.1~esm1) @ xenial2026-07-07ubuntu

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.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

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 45× in last 7d / 83× 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 04:00 UTCEG score recompute
  2. 2026-07-07 04:00 UTCVendor advisory
  3. 2026-07-07 04:00 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 16:16 UTCEG score recompute
  6. 2026-07-06 16:16 UTCGHSA enrichment
  7. 2026-07-06 04:34 UTCEG score recompute
  8. 2026-07-06 04:34 UTCGHSA enrichment
  9. 2026-07-05 16:53 UTCEG score recompute
  10. 2026-07-05 16:53 UTCVendor advisory
  11. 2026-07-05 16:53 UTCGHSA enrichment
  12. 2026-07-05 05:03 UTCEG score recompute
  13. 2026-07-05 05:03 UTCVendor advisory
  14. 2026-07-05 05:03 UTCGHSA enrichment
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 17:22 UTCEG score recompute
  18. 2026-07-04 17:22 UTCVendor advisory
  19. 2026-07-04 17:22 UTCGHSA enrichment
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 05:43 UTCEG score recompute
  22. 2026-07-04 05:42 UTCGHSA enrichment
  23. 2026-07-03 18:01 UTCEG score recompute
  24. 2026-07-03 18:01 UTCVendor advisory
  25. 2026-07-03 18:01 UTCGHSA enrichment
Show 58 more
  1. 2026-07-03 06:20 UTCEG score recompute
  2. 2026-07-03 06:20 UTCGHSA enrichment
  3. 2026-07-02 18:40 UTCEG score recompute
  4. 2026-07-02 18:40 UTCVendor advisory
  5. 2026-07-02 18:40 UTCGHSA enrichment
  6. 2026-07-02 07:00 UTCEG score recompute
  7. 2026-07-02 07:00 UTCVendor advisory
  8. 2026-07-02 07:00 UTCGHSA enrichment
  9. 2026-07-01 19:18 UTCEG score recompute
  10. 2026-07-01 19:18 UTCVendor advisory
  11. 2026-07-01 19:18 UTCGHSA enrichment
  12. 2026-07-01 15:06 UTCEPSS rescore
  13. 2026-07-01 15:06 UTCEPSS rescore
  14. 2026-07-01 07:39 UTCEG score recompute
  15. 2026-07-01 07:39 UTCVendor advisory
  16. 2026-07-01 07:39 UTCGHSA enrichment
  17. 2026-06-30 23:22 UTCEPSS rescore
  18. 2026-06-30 19:59 UTCEG score recompute
  19. 2026-06-30 19:59 UTCVendor advisory
  20. 2026-06-30 19:58 UTCGHSA enrichment
  21. 2026-06-30 08:18 UTCEG score recompute
  22. 2026-06-30 08:18 UTCVendor advisory
  23. 2026-06-30 08:18 UTCGHSA enrichment
  24. 2026-06-29 20:39 UTCEG score recompute
  25. 2026-06-29 20:39 UTCVendor advisory
  26. 2026-06-29 20:39 UTCGHSA enrichment
  27. 2026-06-29 14:06 UTCEPSS rescore
  28. 2026-06-29 08:59 UTCEG score recompute
  29. 2026-06-29 08:59 UTCVendor advisory
  30. 2026-06-29 08:59 UTCGHSA enrichment
  31. 2026-06-28 21:19 UTCEG score recompute
  32. 2026-06-28 21:18 UTCGHSA enrichment
  33. 2026-06-28 14:07 UTCEPSS rescore
  34. 2026-06-28 09:39 UTCEG score recompute
  35. 2026-06-28 09:39 UTCVendor advisory
  36. 2026-06-28 09:38 UTCGHSA enrichment
  37. 2026-06-28 04:56 UTCEPSS rescore
  38. 2026-06-28 04:56 UTCEPSS rescore
  39. 2026-06-27 21:59 UTCEG score recompute
  40. 2026-06-27 21:59 UTCVendor advisory
  41. 2026-06-27 21:59 UTCGHSA enrichment
  42. 2026-06-27 10:18 UTCEG score recompute
  43. 2026-06-27 10:18 UTCVendor advisory
  44. 2026-06-27 10:18 UTCGHSA enrichment
  45. 2026-06-27 03:08 UTCEPSS rescore
  46. 2026-06-26 22:38 UTCEG score recompute
  47. 2026-06-26 22:38 UTCVendor advisory
  48. 2026-06-26 22:38 UTCGHSA enrichment
  49. 2026-06-26 10:58 UTCEG score recompute▼ 0.70
  50. 2026-06-26 10:58 UTCVendor advisory
  51. 2026-06-26 10:58 UTCGHSA enrichment
  52. 2026-06-26 03:53 UTCNVD updateCVSS v3 → 7.5
  53. 2026-06-25 19:46 UTCEG score recompute
  54. 2026-06-25 19:46 UTCVendor advisory
  55. 2026-06-25 19:46 UTCGHSA enrichment
  56. 2026-06-25 13:49 UTCEPSS rescore
  57. 2026-06-25 08:06 UTCEG score recompute
  58. 2026-06-25 08:05 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-12490?
CVE-2026-12490 is a high vulnerability published on June 25, 2026. When a provide-xfr is given with a tls-auth-name, a secondary requesting a transfer should provide a client certificate with that name. However, no client certificate is needed when the request comes in over TLS over the regular tls-port (and not the tls-auth-port) or over over TCP over the regular…
When was CVE-2026-12490 disclosed?
CVE-2026-12490 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-12490 actively exploited?
CVE-2026-12490 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-12490?
CVE-2026-12490 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-12490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-12490, 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

Explore the affected products and dependency analysis for CVE-2026-12490

Explore →

Is Your Infrastructure Affected by CVE-2026-12490?

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

Start Free Scan →Browse All CVEs