Skip to content
Fencer Vulns
critical 9.3

CVE-2009-1886 in the critical feed json

Multiple format string vulnerabilities in client/client.c in smbclient in Samba 3.2.0 through 3.2.12 might allow context-dependent attacker…

published 2009-06-24 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1881

cvss
9.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.2%
EPSS 12.2% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

Multiple format string vulnerabilities in client/client.c in smbclient in Samba 3.2.0 through 3.2.12 might allow context-dependent attackers to execute arbitrary code via format string specifiers in a filename.

Patch / fix

  • samba Debian 14, Debian 13, Debian 12 2:3.3.6-1

debian advisories DEBIAN-CVE-2009-1886

  • samba openSUSE Tumbleweed 4.5.0-1.1
  • cifs-utils openSUSE Tumbleweed 6.5-1.5

opensuse advisories openSUSE-SU-2024:10069-1openSUSE-SU-2024:10334-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-1886 updated

samba format string vulnerabilities

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-33053)
  2. Published

Exploit prediction

12.22% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-33053 Samba 3.3.5 - Format String / Security Bypass remote, 2009-05-19

CVSS scores

assigned by version score vector
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-134 Use of Externally-Controlled Format String

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.