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.
CVE-2026-12490
Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. NVD baseline CVSS 7.5; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 38(Track)EG Risk 38/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 computedSeverity75% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
June 25, 2026
Last Modified
June 26, 2026
Advisory Details (1)
Auto-updated Jun 25, 2026Vendor 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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| ubuntu | nsd3 (4.1.7-1ubuntu0.1~esm1) @ xenial | 2026-08-30 | ubuntu |
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
(4 across 4 ecosystems)
Alpine:v3.24(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nsd | — | 4.14.3-r0 | — |
Debian:12(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nsd | 4.10.1-1 ... 4.9.1-1 (24 versions) | — | — |
Debian:13(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nsd | 4.12.0-1 ... 4.15.1-1 (15 versions) | — | — |
Debian:14(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| nsd | 4.12.0-1 ... 4.14.2-1 (11 versions) | 4.14.3-1 | — |
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 5× 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.
Showing the most recent 100 of 295 total refreshes for this CVE.
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 09:36 UTCEPSS rescore
- 2026-09-10 09:34 UTCEPSS rescore
- 2026-09-07 16:01 UTCEPSS rescore
- 2026-09-06 13:47 UTCEPSS rescore
- 2026-09-04 05:06 UTCEPSS rescore
- 2026-09-02 14:11 UTCEPSS rescore
- 2026-09-01 13:53 UTCEPSS rescore
- 2026-09-01 04:39 UTCEPSS rescore
- 2026-08-30 19:45 UTCEG score recompute
- 2026-08-30 19:45 UTCVendor advisory
- 2026-08-30 19:45 UTCGHSA enrichment
- 2026-08-30 19:17 UTCEPSS rescore
- 2026-08-30 01:21 UTCEPSS rescore
- 2026-08-28 21:40 UTCEPSS rescore
- 2026-08-28 02:57 UTCEG score recompute
- 2026-08-28 02:57 UTCVendor advisory
- 2026-08-28 02:57 UTCGHSA enrichment
- 2026-08-27 14:24 UTCEPSS rescore
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 00:56 UTCEG score recompute
- 2026-08-25 00:56 UTCVendor advisory
- 2026-08-25 00:56 UTCGHSA enrichment
- 2026-08-24 13:17 UTCEG score recompute
- 2026-08-24 13:17 UTCVendor advisory
Show 75 moreShow fewer
- 2026-08-24 13:17 UTCGHSA enrichment
- 2026-08-23 22:22 UTCVendor advisory
- 2026-08-23 22:22 UTCGHSA enrichment
- 2026-08-23 10:27 UTCVendor advisory
- 2026-08-23 10:27 UTCGHSA enrichment
- 2026-08-22 22:42 UTCVendor advisory
- 2026-08-22 22:42 UTCGHSA enrichment
- 2026-08-22 11:01 UTCEG score recompute
- 2026-08-22 11:01 UTCVendor advisory
- 2026-08-22 11:01 UTCGHSA enrichment
- 2026-08-21 23:48 UTCEPSS rescore
- 2026-08-21 18:11 UTCVendor advisory
- 2026-08-21 18:11 UTCGHSA enrichment
- 2026-08-21 06:31 UTCEG score recompute
- 2026-08-21 06:31 UTCVendor advisory
- 2026-08-21 06:31 UTCGHSA enrichment
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 18:51 UTCVendor advisory
- 2026-08-20 18:51 UTCGHSA enrichment
- 2026-08-20 07:12 UTCEG score recompute
- 2026-08-20 07:12 UTCVendor advisory
- 2026-08-20 07:12 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-19 13:16 UTCVendor advisory
- 2026-08-19 13:16 UTCGHSA enrichment
- 2026-08-19 01:37 UTCEG score recompute
- 2026-08-19 01:37 UTCVendor advisory
- 2026-08-19 01:36 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 09:30 UTCVendor advisory
- 2026-08-17 09:30 UTCGHSA enrichment
- 2026-08-16 21:51 UTCEG score recompute
- 2026-08-16 21:51 UTCVendor advisory
- 2026-08-16 21:51 UTCGHSA enrichment
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 10:11 UTCEG score recompute
- 2026-08-16 10:11 UTCVendor advisory
- 2026-08-16 10:11 UTCGHSA enrichment
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 22:32 UTCVendor advisory
- 2026-08-15 22:32 UTCGHSA enrichment
- 2026-08-15 10:50 UTCEG score recompute
- 2026-08-15 10:50 UTCVendor advisory
- 2026-08-15 10:50 UTCGHSA enrichment
- 2026-08-15 01:30 UTCEPSS rescore
- 2026-08-14 23:10 UTCVendor advisory
- 2026-08-14 23:10 UTCGHSA enrichment
- 2026-08-14 11:30 UTCVendor advisory
- 2026-08-14 11:30 UTCGHSA enrichment
- 2026-08-13 23:51 UTCEG score recompute
- 2026-08-13 23:51 UTCVendor advisory
- 2026-08-13 23:51 UTCGHSA enrichment
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-13 12:07 UTCVendor advisory
- 2026-08-13 12:07 UTCGHSA enrichment
- 2026-08-13 00:27 UTCEG score recompute
- 2026-08-13 00:27 UTCVendor advisory
- 2026-08-13 00:27 UTCGHSA enrichment
- 2026-08-12 13:50 UTCEPSS rescore
- 2026-08-12 12:48 UTCVendor advisory
- 2026-08-12 12:48 UTCGHSA enrichment
- 2026-08-12 00:55 UTCEG score recompute
- 2026-08-12 00:55 UTCVendor advisory
- 2026-08-12 00:55 UTCGHSA enrichment
- 2026-08-11 13:42 UTCEPSS rescore
- 2026-08-11 13:16 UTCVendor advisory
- 2026-08-11 13:16 UTCGHSA enrichment
- 2026-08-11 01:37 UTCEG score recompute
- 2026-08-11 01:37 UTCVendor advisory
- 2026-08-11 01:37 UTCGHSA enrichment
- 2026-08-10 23:59 UTCEPSS rescore
- 2026-08-10 13:58 UTCVendor advisory
- 2026-08-10 13:57 UTCGHSA enrichment
- 2026-08-10 02:18 UTCVendor advisory
- 2026-08-10 02:18 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-12490?
When was CVE-2026-12490 disclosed?
Is CVE-2026-12490 actively exploited?
What is the CVSS score of CVE-2026-12490?
How do I remediate CVE-2026-12490?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-12490
Is Your Infrastructure Affected by CVE-2026-12490?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.