CVE-2025-10230Disclosure

LOWCVSS 10.0 · CRITICAL

Signal is active with 2 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

A flaw was found in Samba, in the front-end WINS hook handling: NetBIOS names from registration packets are passed to a shell without proper validation or escaping. Unsanitized NetBIOS name data from WINS registration packets are inserted into a shell command and executed by the Samba Active Directory Domain Controller’s wins hook, allowing an unauthenticated network attacker to achieve remote command execution as the Samba process.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-78

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

2 mentions across 1 observed day

What's happening

Technical details provided in 1 signal
Disclosure: 1 classified signal
General: 1 classified signal
2 total mentions across 1 day

Deep dive

Activity timeline2 mentions / 1d

Signal classification2 categories

Disclosure

150.0%

General

150.0%

Referenced assets1 URL

By indicator

https://cvebrief.com/cve/CVE-2025-10230/

Full discourse2 posts

CVE Brief@DailyCVEBrief46d
Disclosure
LOOK BACK — Samba has rejected shell metacharacters in WINS hook names since 1999, and the manpage promised it. When Samba 4 rewrote the WINS server for AD domain controllers in 2006, that check did not come along. CVE-2025-10230 shipped for 13 years at CVSS 10.0. https://t.co/Np55WsnAen
Post summary
The post highlights that Samba’s CVE‑2025‑10230, a critical flaw with CVSS 10.0, remained unpatched for 13 years after a missing check in the WINS server rewrite.
1000032
29 followersView on X
CVE Brief@DailyCVEBrief46d
General
Full Look Back: what a 2006 port dropped, why the fix was a 1999 loop copied forward, and why a CVSS 10.0 never reached KEV: https://cvebrief.com/cve/CVE-2025-10230/ https://t.co/5RSTWn7z7K
Post summary
The tweet provides a historical overview of CVE-2025-10230, noting its high CVSS score and why it never reached KEV, but offers no technical or exploit details.
0000026
29 followersView on X

Explore more

Back to dashboard