Cyber Resilience

CVE-2026-45038

Tabby ≤ 1.0.233

Public PoC
Published
15 May 2026
Modified
17 June 2026
Patch / advisory
CVSS Score v4 8.4
Click a component to see what it means
Raw vectorCVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/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
EPSS Score 0.0018 8th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-45038 is a high-severity Improper Neutralization of Escape, Meta, or Control Sequences (CWE-150) vulnerability in Tabby Tabby. Its CVSS base score is 8.4 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 8th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Tabby (formerly Terminus) is a highly configurable terminal emulator. Prior to 1.0.233, since Tabby does not escape control characters from file paths when dragging and dropping a file into it, code execution can be achieved. This vulnerability is fixed in…

more

1.0.233.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-45036Same product: Tabby Tabby
CVE-2026-45035Same product: Tabby Tabby
CVE-2026-46709Same product: Tabby Tabby
CVE-2026-45037Same product: Tabby Tabby
CVE-2026-21439Shared CWE-150
CVE-2026-40505Shared CWE-150
CVE-2026-49147Shared CWE-150
CVE-2026-45803Shared CWE-150
CVE-2024-36052Shared CWE-150
CVE-2025-62845Shared CWE-150

Affected Assets

tabby
tabby
≤ 1.0.233

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V1.2.10
  • V1.3.12

Mitigating Controls (NIST 800-53 r5) AI

SI-10 requires validation/sanitization of inputs that directly stops escape/meta/control sequences from reaching downstream components.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input neutralization and escaping to prevent this class of flaw.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect the weakness but does not itself implement neutralization.

prevents

Secure development lifecycle mandates input validation and output encoding that directly neutralizes escape/meta sequences.

prevents

Application security requirements explicitly call for controls against injection and malformed input sequences.

prevents

Secure architecture principles reduce attack surface but do not prescribe specific neutralization techniques.

prevents

Secure coding standards require proper escaping and neutralization of control characters before downstream processing.

References