Skip to main content
No exploitation reportedFix available

CVE-2026-12490

No exploitation reported by the sources we read.

  • Published2026-06-25
  • Fixed in4.14.3
  • WeaknessCWE-284 · CWE-306

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2026-06-2507:16CVE publishedNVD

Versions per branch

NVD
Nlnetlabs nsd
BranchAffectedFixed in
4.14< 4.14.34.14.3

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As NLnet Labs, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • NLnet Labs NSDother versions: not affected
    Affected
    • ≥ 4.10.1, < 4.14.3fixed in 4.14.3semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-06-25

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • nsdUbuntu:Pro:26.04:LTSall versions · fixed in 4.14.0-1ubuntu0.1~esm1
  • nsdUbuntu:26.10all versions · no fixed version listed
  • nsdopenSUSE:Tumbleweedall versions · fixed in 4.14.3-1.1
  • nsdopenSUSE:Leap 16.0all versions · fixed in 4.14.3-bp160.1.1
  • nsdDebian:14all versions · fixed in 4.14.3-1
  • nsdDebian:13all versions · no fixed version listed
  • nsdDebian:12all versions · no fixed version listed
  • nsdAlpine:v3.24all versions · fixed in 4.14.3-r0

Full record on NVD

Fix

  1. Update Nlnetlabs nsd to 4.14.3

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof of concept
Metasploit modules
none listed
Metasploit Framework

Sources

  • CISA-ADPSSVC decisionnone2026-06-25
  • CNACVSS 4.08.2known since 2026-10-26
  • NVDCVSS 3.17.5read 2026-10-26
  • CNAweakness (CWE)CWE-284, CWE-306known since 2026-10-26
  • FIRST EPSSEPSS score0.2 %2026-11-08
  • OSVaffected packages—
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-06-25
Last Modified
2026-10-25
NVD status
Analyzed
GitHub Advisory
GHSA-27xx-c7vg-hjjj

Frequently asked questions

What is CVE-2026-12490?

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.

Is CVE-2026-12490 actively exploited?

Active exploitation of CVE-2026-12490 has not been confirmed. Its EPSS score was 0.2% on 2026-11-08, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-12490?

CVE-2026-12490 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running nsd? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month

Sources for this record