dbcve.org
DyeApplication · Mattiebee

CVE-2026-35197

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
dye is a portable and respectful color library for shell scripts. Prior to 1.1.1, certain dye template expressions would result in execution of arbitrary code. This issue was discovered and fixed by dye's author, and is not known to be exploited. This vulnerability is fixed in 1.1.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The dye library (a color library for shell scripts) versions prior to 1.1.1 contain a code injection vulnerability where certain template expressions allow execution of arbitrary code. This is a critical command injection flaw in the template processing functionality of the library.

MitigationUpgrade dye to version 1.1.1 or later. Additionally, audit any codebase that uses dye to understand if untrusted input is being passed to template expressions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DyeApplication
Affected:= 1.1.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate dye library installation
    Run 'find / -name "dye*" -o -name "*dye*" 2>/dev/null' or check common locations like /usr/local/lib, ~/.local/lib, or within project directories using grep -r "dye" to find imported library files
    Affected if dye library files are found in the system or project
  2. Check dye library version
    Inspect the dye library source file or package metadata. Look for a version string in the main library file (often dye.sh, dye, or similar). Run 'grep -i version <filename>' or check for VERSION variable in the library
    Affected if The installed version is 1.1.0 exactly (not 1.1.1 or later)
  3. Identify scripts using dye library
    Search for shell scripts that source or import the dye library: 'grep -r "source.*dye\|\. dye\|require.*dye" .' or 'grep -r "dye" *.sh' in project directories
    Affected if Shell scripts that import dye library are found in the environment
  4. Check for template expression usage
    Examine the identified scripts for template expressions - look for patterns like '{{' '}}' or similar templating syntax being passed to dye functions, or dynamic command construction using dye output
    Affected if Scripts use dye's template or interpolation features with user-controlled input
  5. Verify code injection potential
    Review how dye library output is used in the scripts - check if dye-generated strings are passed to 'eval', 'bash -c', or directly to shell execution context without sanitization
    Affected if Dye library output flows into shell execution commands without validation

You are affected if the dye library version is 1.1.0 and any shell scripts use dye's template expressions with potentially untrusted input that could be injected into shell execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade dye to version 1.1.1 or later. Additionally, audit any codebase that uses dye to understand if untrusted input is being passed to template expressions.

Recommended fix High confidence

1.1.1

  1. Identify the current installed version of the dye package
  2. Upgrade dye to version 1.1.1 or the latest stable version available
  3. Verify the upgrade was successful by confirming the installed version is 1.1.1 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dye Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35197 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35197 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data