CVE-2026-12490

unknown

Published 2026-06-25 · Modified 2026-06-25

💬 Discuss on Community ✚ Propose mitigation

CVSS v3

—

CVSS v4 NEW

8.2

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

VIR risk

—

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.

Predictions

Exploit likelihood

20%

Patch ETA

—

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.

✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

Ubuntu Fixed 6 releases

Version	Status	Fixed in
xenial	Fixed	`4.1.7-1ubuntu0.1~esm1`
resolute	Fixed	`4.14.0-1ubuntu0.1~esm1`
noble	Fixed	`4.8.0-1ubuntu0.1~esm1`
jammy	Fixed	`4.3.9-1ubuntu0.1~esm1`
focal	Fixed	`4.1.26-1ubuntu0.1~esm1`
bionic	Fixed	`4.1.17-1ubuntu0.1~esm1`

References

CWEs

CWE-284 CWE-306

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.