tsParticles: Generated release notes can execute shell commands in the stable publish workflow
Affects tsParticles 4.0.0 through 4.3.1, where the stable publish workflow renders generated release notes into a Bash command. The fix is in 4.3.2.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.3.2
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The stable publish workflow runs and renders the generated release body into a Bash command. The release-note text contains shell metacharacters, such as command substitution, which can come from contributor-controlled content like merged PR titles. The vulnerable sink is still present in v4.3.1 and current main, so affected releases include v4.3.1 and earlier.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Reach: unknown (data gap). No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
CVE-2026-76826 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects tsparticles; fixed in 4.3.2.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 4.3.2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
tsParticles, a TypeScript library for particle animations, is affected by a flaw in its stable publish workflow that lets an attacker run shell commands through crafted release-note text, which can allow changes to generated artifacts or workspace scripts and affect later release steps that hold GITHUB_TOKEN and write permissions. The attack can be carried out remotely, without logging in, but it requires a maintainer to start a stable release.
Read the original description
tsParticles is a TypeScript library for creating highly customizable particle animations. From 4.0.0 until 4.3.2, the stable publish workflow interpolates steps.release.outputs.body directly into an echo command in Bash source before writing RAW_RELEASE.md. Contributor-controlled shell metacharacters in generated release-note text can therefore execute when a maintainer starts a stable release, allowing modification of generated artifacts or workspace scripts and affecting later release steps that hold GITHUB_TOKEN and write permissions. This issue is fixed in version 4.3.2.
What to do
Check whether your setup matches what the bug needs.
The stable publish workflow runs and renders the generated release body into a Bash command. The release-note text contains shell metacharacters, such as command substitution, which can come from contributor-controlled content like merged PR titles. The vulnerable sink is still present in v4.3.1 and current main, so affected releases include v4.3.1 and earlier.Upgrade to a fixed version: 4.3.2.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- tsparticles tsparticles
From 4.0.0 · fixed in 4.3.2
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-76826
Is CVE-2026-76826 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The stable publish workflow puts the generated GitHub release body directly into Bash source code. Release-note text containing shell metacharacters, such as command substitution, can run arbitrary shell commands in the publish job, which can modify release artifacts or workspace helper scripts and affect later release steps that hold GITHUB_TOKEN with write permissions.Source: github.com, github.com
Which versions are affected by CVE-2026-76826?
tsparticles: from 4.0.0 before 4.3.2.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 4.0.0 up to 4.3.1 are listed as affected, and the vulnerable sink is still present in v4.3.1 and current main. The setup concerned is a stable publish workflow that builds the release body from generated notes, which can include contributor-controlled text such as merged PR titles. Check the tsparticles version in use and whether that publish workflow renders the generated release body into Bash.Source: github.com, github.com
How do I fix CVE-2026-76826?
Upgrade tsparticles to 4.3.2, the version listed as the fix.Source: github.com, github.com