Samba: samba: remote code execution in printing subsystem via unescaped job description
Red Hat · Red Hat Enterprise Linux 10
A flaw in Red Hat Enterprise Linux 10's Samba printing subsystem passes the client-controlled job description to the configured "print command" via the %J substitution without escaping shell metacharacters. An unauthenticated remote attacker can exploit this by submitting a specially crafted print job description containing unescaped shell characters, leading to remote code execution, though the attack requires a high-complexity condition and no user interaction.
A flaw was found in the Samba printing subsystem. Samba passes the client-controlled job description string to the command configured with the "print command" setting via the "%J" substitution character without escaping shell meta characters. A remote attacker could exploit this vulnerability by sending a specially crafted print job description that contains unescaped shell characters. This could lead to remote code execution on the affected system.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 55 days after disclosure. Public exploit code (PoC-in-GitHub) appeared 10 days after disclosure.
- Disclosedday 0
- Public exploit codePoC-in-GitHub+10 days
- First seen exploitedVulnCheck KEV evidence+55 days
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
What security researchers reported
Not named in any threat report yetAlso mentioned in 8 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Known_Cve | Jun 4, 2026 | Part 1/23 Jun 2026
- Known_Cve | Jun 3, 2026 | Part 1/22 Jun 2026
- Known_Cve | Jun 2, 2026 | Part 1/21 Jun 2026
- Known_Cve | Jun 1, 2026 | Part 1/231 May 2026
- Known_Cve | May 31, 2026 | Part 1/230 May 2026
- Known_Cve | May 30, 2026 | Part 1/229 May 2026
- 2 more on OTX