tailwindcss-3.3.3.tgz: 19 vulnerabilities (highest severity is: 7.5) #442

Vulnerable Library - tailwindcss-3.3.3.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

CVE-2026-93687

Vulnerable Library - braces-3.0.3.tgz

Library home page: https://registry.npmjs.org/braces/-/braces-3.0.3.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • chokidar-3.5.3.tgz
    • ❌ braces-3.0.3.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

braces through 3.0.3 contains a stack overflow vulnerability in the recursive AST walkers that lack depth guards. Attackers can supply deeply nested brace patterns under the character limit to exhaust the call stack and terminate the Node.js process with an uncaught RangeError.

Publish Date: 2026-09-18

URL: CVE-2026-93687

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Step up your Open Source Security Game with Mend here

CVE-2026-73646

Vulnerable Library - postcss-8.4.49.tgz

Tool for transforming styles with JS plugins

Library home page: https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • ❌ postcss-8.4.49.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

PostCSS takes a CSS file and provides an API to analyze and modify its rules by transforming the rules into an Abstract Syntax Tree. Prior to 8.5.18, lib/previous-map.js loadMap() passes attacker-controlled sourceMappingURL values to join(dirname(opts.from), annotation), and loadFile() permits traversed or absolute .map paths, allowing untrusted CSS processed without map: false to disclose sourcesContent from arbitrary reachable .map files through result.map. This issue is fixed in version 8.5.18.

Publish Date: 2026-08-17

URL: CVE-2026-73646

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

Suggested Fix

Type: Upgrade version

Origin: GHSA-r28c-9q8g-f849

Release Date: 2026-08-13

Fix Resolution: postcss - 8.5.18

Step up your Open Source Security Game with Mend here

CVE-2026-69152

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • minimatch-3.1.2.tgz
        • ❌ brace-expansion-1.1.11.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.18, 2.1.4, 3.0.6, and 5.0.9, expand() does not apply maxLength while constructing comma-alternative intermediate arrays or padded sequences, allowing attacker-controlled input to exhaust memory or block the event loop. The fix for CVE-2026-14257 is bypassed by the vulnerability. This issue is fixed in versions 1.1.18, 2.1.4, 3.0.6, and 5.0.9.

Publish Date: 2026-08-03

URL: CVE-2026-69152

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-rgw5-rvv9-x895

Release Date: 2026-08-03

Fix Resolution: brace-expansion - 1.1.18

Step up your Open Source Security Game with Mend here

CVE-2026-45623

Vulnerable Library - postcss-8.4.49.tgz

Tool for transforming styles with JS plugins

Library home page: https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • ❌ postcss-8.4.49.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

PostCSS takes a CSS file and provides an API to analyze and modify its rules by transforming the rules into an Abstract Syntax Tree. In versions 8.5.11 and prior, the PreviousMap parses the /*# sourceMappingURL=PATH */ comment from any CSS string passed to process() and dereferences PATH against the local filesystem with no scheme, allowlist, or traversal check. An attacker who controls the CSS input can cause the host process to read any file readable by Node and leak the first ~10 bytes of its content through the resulting JSON.parse SyntaxError message. The bug also yields a precise file-existence oracle and a controllable-read primitive that may be combined with large-file targets for DoS. The behaviour is triggered with PostCSS's default options — no from, no map, no plugins required — and is therefore reachable from any pipeline that runs untrusted CSS through PostCSS (CMS themes, user-uploaded styles, browser-extension/userstyle processors, build pipelines for third-party packages, blog comment renderers, etc.). This issue has been fixed in version 8.5.12.

Publish Date: 2026-07-27

URL: CVE-2026-45623

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: None
  • Availability Impact: None

Suggested Fix

Type: Upgrade version

Release Date: 2026-07-23

Fix Resolution (postcss): 8.5.12

Direct dependency fix Resolution (tailwindcss): 3.3.4

Step up your Open Source Security Game with Mend here

CVE-2026-33671

Vulnerable Library - picomatch-2.3.1.tgz

Blazing fast and accurate glob matcher written in JavaScript, with no dependencies and full support for standard and extended Bash glob features, including braces, extglobs, POSIX brackets, and regular expressions.

Library home page: https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • micromatch-4.0.8.tgz
    • ❌ picomatch-2.3.1.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to Regular Expression Denial of Service (ReDoS) when processing crafted extglob patterns. Certain patterns using extglob quantifiers such as "+()" and "()", especially when combined with overlapping alternatives or nested extglobs, are compiled into regular expressions that can exhibit catastrophic backtracking on non-matching input. Applications are impacted when they allow untrusted users to supply glob patterns that are passed to "picomatch" for compilation or matching. In those cases, an attacker can cause excessive CPU consumption and block the Node.js event loop, resulting in a denial of service. Applications that only use trusted, developer-controlled glob patterns are much less likely to be exposed in a security-relevant way. This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. If upgrading is not immediately possible, avoid passing untrusted glob patterns to "picomatch". Possible mitigations include disabling extglob support for untrusted patterns by using "noextglob: true", rejecting or sanitizing patterns containing nested extglobs or extglob quantifiers such as "+()" and "()", enforcing strict allowlists for accepted pattern syntax, running matching in an isolated worker or separate process with time and resource limits, and applying application-level request throttling and input validation for any endpoint that accepts glob patterns.

Publish Date: 2026-03-26

URL: CVE-2026-33671

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-c2c7-rcm5-vvqj

Release Date: 2026-03-26

Fix Resolution: picomatch - 2.3.2

Step up your Open Source Security Game with Mend here

CVE-2026-27904

Vulnerable Library - minimatch-3.1.2.tgz

a glob matcher in javascript

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • ❌ minimatch-3.1.2.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4, nested "()" extglobs produce regexps with nested unbounded quantifiers (e.g. "(?:(?:a|b))"), which exhibit catastrophic backtracking in V8. With a 12-byte pattern "(((a|b)))" and an 18-byte non-matching input, "minimatch()" stalls for over 7 seconds. Adding a single nesting level or a few input characters pushes this to minutes. This is the most severe finding: it is triggered by the default "minimatch()" API with no special options, and the minimum viable pattern is only 12 bytes. The same issue affects "+()" extglobs equally. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4 fix the issue.

Publish Date: 2026-02-26

URL: CVE-2026-27904

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-23c5-xmqv-rm74

Release Date: 2026-02-26

Fix Resolution (minimatch): 3.1.4

Direct dependency fix Resolution (tailwindcss): 3.3.4

Step up your Open Source Security Game with Mend here

CVE-2026-27903

Vulnerable Library - minimatch-3.1.2.tgz

a glob matcher in javascript

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • ❌ minimatch-3.1.2.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3, "matchOne()" performs unbounded recursive backtracking when a glob pattern contains multiple non-adjacent "**" (GLOBSTAR) segments and the input path does not match. The time complexity is O(C(n, k)) -- binomial -- where "n" is the number of path segments and "k" is the number of globstars. With k=11 and n=30, a call to the default "minimatch()" API stalls for roughly 5 seconds. With k=13, it exceeds 15 seconds. No memoization or call budget exists to bound this behavior. Any application where an attacker can influence the glob pattern passed to "minimatch()" is vulnerable. The realistic attack surface includes build tools and task runners that accept user-supplied glob arguments (ESLint, Webpack, Rollup config), multi-tenant systems where one tenant configures glob-based rules that run in a shared process, admin or developer interfaces that accept ignore-rule or filter configuration as globs, and CI/CD pipelines that evaluate user-submitted config files containing glob patterns. An attacker who can place a crafted pattern into any of these paths can stall the Node.js event loop for tens of seconds per invocation. The pattern is 56 bytes for a 5-second stall and does not require authentication in contexts where pattern input is part of the feature. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3 fix the issue.

Publish Date: 2026-02-26

URL: CVE-2026-27903

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Release Date: 2026-02-26

Fix Resolution (minimatch): 3.1.4

Direct dependency fix Resolution (tailwindcss): 3.3.4

Step up your Open Source Security Game with Mend here

CVE-2026-26996

Vulnerable Library - minimatch-3.1.2.tgz

a glob matcher in javascript

Library home page: https://registry.npmjs.org/minimatch/-/minimatch-3.1.2.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • ❌ minimatch-3.1.2.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Versions prior to 10.2.1, 3.1.3, 4.2.4, 5.1.7, 6.2.1, 7.4.7, 8.0.5, and 9.0.6 are vulnerable to Regular Expression Denial of Service (ReDoS) when a glob pattern contains many consecutive * wildcards followed by a literal character that doesn't appear in the test string. Each * compiles to a separate [^/]*? regex group, and when the match fails, V8's regex engine backtracks exponentially across all possible splits. The time complexity is O(4^N) where N is the number of * characters. With N=15, a single minimatch() call takes ~2 seconds. With N=34, it hangs effectively forever. Any application that passes user-controlled strings to minimatch() as the pattern argument is vulnerable to DoS.
This issue has been fixed in versions 10.2.1, 3.1.3, 4.2.4, 5.1.7, 6.2.1, 7.4.7, 8.0.5, and 9.0.6.
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2026-02-20

URL: CVE-2026-26996

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-3ppc-4f35-3m26

Release Date: 2026-02-20

Fix Resolution: minimatch - 3.1.3

Step up your Open Source Security Game with Mend here

CVE-2026-14257

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • minimatch-3.1.2.tgz
        • ❌ brace-expansion-1.1.11.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

brace-expansion through 5.0.7 is vulnerable to denial of service via memory exhaustion. The expand() function limits the number of results with a max option (default 100,000) but does not bound the length of each result string. By chaining multiple brace groups, an attacker keeps the result count under the limit while making each result progressively longer, so total memory scales with both count and string length until the process hits a fatal, uncatchable out-of-memory error. About 7.5 KB of input ('{a,b}'.repeat(1500)) crashes a default Node.js process. Any application that passes attacker-influenced strings to brace-expansion.expand() - directly or transitively via minimatch / glob brace patterns - can be crashed by a small request. Fixed in 5.0.8 by adding a maxLength option (default 4,000,000) that bounds accumulated output and intermediate arrays.

Publish Date: 2026-07-23

URL: CVE-2026-14257

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-mh99-v99m-4gvg

Release Date: 2026-07-23

Fix Resolution: brace-expansion - 1.1.17

Step up your Open Source Security Game with Mend here

CVE-2026-13149

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • minimatch-3.1.2.tgz
        • ❌ brace-expansion-1.1.11.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

brace-expansion through 5.0.6 is vulnerable to denial of service. The expand() function exhibits exponential-time complexity in the number of consecutive non-expanding '{}' brace groups. An attacker who passes a crafted string to expand(), directly or transitively, can cause significant CPU consumption and event-loop blocking. The max option does not mitigate this, as it bounds the output size rather than the recursion work.

Publish Date: 2026-06-30

URL: CVE-2026-13149

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-3jxr-9vmj-r5cp

Release Date: 2026-06-30

Fix Resolution: brace-expansion - 1.1.16

Step up your Open Source Security Game with Mend here

CVE-2026-102278

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • minimatch-3.1.2.tgz
        • ❌ brace-expansion-1.1.11.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.20, 2.1.6, 3.0.8, and 5.0.11, deeply nested brace groups cause expand_() to recurse once per nesting level at comma-member and single-set expansion sites, exhausting the native stack before output limits can apply and potentially terminating the Node.js process. expand_ performs uncontrolled recursion for nested brace alternatives and single-part sets. deeply nested brace groups supplied as an untrusted pattern. expand_ is affected. expand is affected. Comma members is affected. Single set is affected. native stack exhaustion during nested sub-expansion. process-terminating denial of service. This issue is fixed in versions 1.1.20, 2.1.6, 3.0.8, and 5.0.11.

Publish Date: 2026-09-28

URL: CVE-2026-102278

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Release Date: 2026-09-28

Fix Resolution (brace-expansion): 1.1.20

Direct dependency fix Resolution (tailwindcss): 3.3.4

Step up your Open Source Security Game with Mend here

CVE-2026-102276

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • minimatch-3.1.2.tgz
        • ❌ brace-expansion-1.1.11.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.19, 2.1.5, 3.0.7, and 5.0.10, crafted brace patterns can exhaust the native stack in parseCommaParts because parseCommaParts recursively processes the remainder once per brace group and uses push.apply to pass every element of a very large comma-part array as a function argument. Patterns containing many comma-separated brace groups trigger the recursive path, while the large array triggers the argument-array path without deep recursion. These paths cause recursive and argument-array native stack exhaustion before max or maxLength can limit output, potentially terminating the Node.js process in a process-terminating denial of service. This issue is fixed in versions 1.1.19, 2.1.5, 3.0.7, and 5.0.10.

Publish Date: 2026-09-28

URL: CVE-2026-102276

CVSS 3 Score Details (7.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Release Date: 2026-09-28

Fix Resolution (brace-expansion): 1.1.19

Direct dependency fix Resolution (tailwindcss): 3.3.4

Step up your Open Source Security Game with Mend here

CVE-2026-33750

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • minimatch-3.1.2.tgz
        • ❌ brace-expansion-1.1.11.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to versions 5.0.5, 3.0.2, 2.0.3, and 1.1.13, a brace pattern with a zero step value (e.g., "{1..2..0}") causes the sequence generation loop to run indefinitely, making the process hang for seconds and allocate heaps of memory. Versions 5.0.5, 3.0.2, 2.0.3, and 1.1.13 fix the issue. As a workaround, sanitize strings passed to "expand()" to ensure a step value of "0" is not used.

Publish Date: 2026-03-27

URL: CVE-2026-33750

CVSS 3 Score Details (6.5)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-f886-m6hf-6m8v

Release Date: 2026-03-27

Fix Resolution: brace-expansion - 1.1.13

Step up your Open Source Security Game with Mend here

CVE-2026-41305

Vulnerable Library - postcss-8.4.49.tgz

Tool for transforming styles with JS plugins

Library home page: https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • ❌ postcss-8.4.49.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

PostCSS takes a CSS file and provides an API to analyze and modify its rules by transforming the rules into an Abstract Syntax Tree. Versions prior to 8.5.10 do not escape "</style>" sequences when stringifying CSS ASTs. When user-submitted CSS is parsed and re-stringified for embedding in HTML "<style>" tags, "</style>" in CSS values breaks out of the style context, enabling XSS. Version 8.5.10 fixes the issue.

Publish Date: 2026-04-24

URL: CVE-2026-41305

CVSS 3 Score Details (6.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: Required
  • Scope: Changed
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: Low
  • Availability Impact: None

Suggested Fix

Type: Upgrade version

Origin: GHSA-qx2v-qp2m-jg93

Release Date: 2026-04-24

Fix Resolution (postcss): 8.5.10

Direct dependency fix Resolution (tailwindcss): 3.3.4

Step up your Open Source Security Game with Mend here

CVE-2026-104844

Vulnerable Library - postcss-selector-parser-6.0.13.tgz

Library home page: https://registry.npmjs.org/postcss-selector-parser/-/postcss-selector-parser-6.0.13.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • ❌ postcss-selector-parser-6.0.13.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

PostCSS Selector Parser is a CSS selector parser that integrates with PostCSS but does not require it. Prior to 7.1.6, src/parser.js splitWord() can receive a flat selector as one word token carrying many class or ID indexes because period and hash characters are not tokenizer word delimiters. The uniqs() deduplication and per-index class and ID membership checks repeatedly scan the class and ID index arrays, while a separate Sass-interpolation filtering pass also performs repeated linear scanning. Together, these passes make parsing quadratic in the number of indexes and allow a crafted selector to occupy a synchronous parser thread. The maxNestingDepth guard does not mitigate the issue because the hostile selector can have zero nesting depth. Only consumers that synchronously parse untrusted selectors in an exposed request path are affected; ordinary build-time parsing of trusted sources is not affected. This issue is fixed in version 7.1.6.

Publish Date: 2026-10-02

URL: CVE-2026-104844

CVSS 3 Score Details (5.9)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Origin: GHSA-rj75-hqrm-r3gf

Release Date: 2026-10-02

Fix Resolution: postcss-selector-parser - 7.1.6

Step up your Open Source Security Game with Mend here

CVE-2026-69153

Vulnerable Library - postcss-8.4.49.tgz

Tool for transforming styles with JS plugins

Library home page: https://registry.npmjs.org/postcss/-/postcss-8.4.49.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • ❌ postcss-8.4.49.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

PostCSS takes a CSS file and provides an API to analyze and modify its rules by transforming the rules into an Abstract Syntax Tree. Prior to 8.5.19, if from is unset, an attacker can cause PreviousMap.loadFile() to read an unintended source-map file by supplying an absolute or directory-traversal sourceMappingURL. The resulting map’s sources and sourcesContent may then be exposed to the application. This issue is fixed in version 8.5.19.

Publish Date: 2026-08-03

URL: CVE-2026-69153

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: Low
  • Integrity Impact: None
  • Availability Impact: None

Suggested Fix

Type: Upgrade version

Origin: GHSA-fxqj-rqcc-2cmp

Release Date: 2026-08-03

Fix Resolution: postcss - 8.5.23

Step up your Open Source Security Game with Mend here

CVE-2026-33672

Vulnerable Library - picomatch-2.3.1.tgz

Blazing fast and accurate glob matcher written in JavaScript, with no dependencies and full support for standard and extended Bash glob features, including braces, extglobs, POSIX brackets, and regular expressions.

Library home page: https://registry.npmjs.org/picomatch/-/picomatch-2.3.1.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • micromatch-4.0.8.tgz
    • ❌ picomatch-2.3.1.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

Picomatch is a glob matcher written JavaScript. Versions prior to 4.0.4, 3.0.2, and 2.3.2 are vulnerable to a method injection vulnerability affecting the "POSIX_REGEX_SOURCE" object. Because the object inherits from "Object.prototype", specially crafted POSIX bracket expressions (e.g., "[[:constructor:]]") can reference inherited method names. These methods are implicitly converted to strings and injected into the generated regular expression. This leads to incorrect glob matching behavior (integrity impact), where patterns may match unintended filenames. The issue does not enable remote code execution, but it can cause security-relevant logic errors in applications that rely on glob matching for filtering, validation, or access control. All users of affected "picomatch" versions that process untrusted or user-controlled glob patterns are potentially impacted. This issue is fixed in picomatch 4.0.4, 3.0.2 and 2.3.2. Users should upgrade to one of these versions or later, depending on their supported release line. If upgrading is not immediately possible, avoid passing untrusted glob patterns to picomatch. Possible mitigations include sanitizing or rejecting untrusted glob patterns, especially those containing POSIX character classes like "[[:...:]]"; avoiding the use of POSIX bracket expressions if user input is involved; and manually patching the library by modifying "POSIX_REGEX_SOURCE" to use a null prototype.

Publish Date: 2026-03-26

URL: CVE-2026-33672

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: Low
  • Availability Impact: None

Suggested Fix

Type: Upgrade version

Origin: GHSA-3v7f-55p6-f55p

Release Date: 2026-03-26

Fix Resolution: picomatch - 2.3.2

Step up your Open Source Security Game with Mend here

CVE-2026-102277

Vulnerable Library - brace-expansion-1.1.11.tgz

Brace expansion as known from sh/bash

Library home page: https://registry.npmjs.org/brace-expansion/-/brace-expansion-1.1.11.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • sucrase-3.34.0.tgz
    • glob-7.1.6.tgz
      • minimatch-3.1.2.tgz
        • ❌ brace-expansion-1.1.11.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

The brace-expansion library generates arbitrary strings containing a common prefix and suffix. Prior to 1.1.21, 2.1.7, 3.0.9, and 5.0.12, the expand function handles untrusted {a},b}-shaped patterns with many trailing closing braces by restarting its scan once for each trailing closing brace. The successive full-input rescans with linear working-string growth cause quadratic CPU time and memory pressure that can block the Node.js event loop. The process eventually recovers, making the impact a recoverable CPU denial of service. This issue is fixed in versions 1.1.21, 2.1.7, 3.0.9, and 5.0.12.

Publish Date: 2026-09-28

URL: CVE-2026-102277

CVSS 3 Score Details (5.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

Suggested Fix

Type: Upgrade version

Release Date: 2026-09-28

Fix Resolution (brace-expansion): 1.1.21

Direct dependency fix Resolution (tailwindcss): 3.3.4

Step up your Open Source Security Game with Mend here

CVE-2026-33532

Vulnerable Library - yaml-2.3.3.tgz

Library home page: https://registry.npmjs.org/yaml/-/yaml-2.3.3.tgz

Sample Path to Dependency File: /playground/package.json

Path to vulnerable library: /playground/package.json

Dependency Hierarchy:

• tailwindcss-3.3.3.tgz (Root Library)
  • postcss-load-config-4.0.1.tgz
    • ❌ yaml-2.3.3.tgz (Vulnerable Library)

Found in HEAD commit: 2c2e4a13b710ceb8f65cd32664895e4278834389

Found in base branch: develop

Vulnerability Details

"yaml" is a YAML parser and serialiser for JavaScript. Parsing a YAML document with a version of "yaml" on the 1.x branch prior to 1.10.3 or on the 2.x branch prior to 2.8.3 may throw a RangeError due to a stack overflow. The node resolution/composition phase uses recursive function calls without a depth bound. An attacker who can supply YAML for parsing can trigger a "RangeError: Maximum call stack size exceeded" with a small payload (~2–10 KB). The "RangeError" is not a "YAMLParseError", so applications that only catch YAML-specific errors will encounter an unexpected exception type. Depending on the host application's exception handling, this can fail requests or terminate the Node.js process. Flow sequences allow deep nesting with minimal bytes (2 bytes per level: one "[" and one "]"). On the default Node.js stack, approximately 1,000–5,000 levels of nesting (2–10 KB input) exhaust the call stack. The exact threshold is environment-dependent (Node.js version, stack size, call stack depth at invocation). Note: the library's "Parser" (CST phase) uses a stack-based iterative approach and is not affected. Only the compose/resolve phase uses actual call-stack recursion. All three public parsing APIs are affected: "YAML.parse()", "YAML.parseDocument()", and "YAML.parseAllDocuments()". Versions 1.10.3 and 2.8.3 contain a patch.

Publish Date: 2026-03-26

URL: CVE-2026-33532

CVSS 3 Score Details (4.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

Suggested Fix

Type: Upgrade version

Origin: GHSA-48c2-rrv3-qjmp

Release Date: 2026-03-26

Fix Resolution: yaml - 2.8.3

Step up your Open Source Security Game with Mend here