Report · Reddit CybersecurityAbout CVE-2026-43945Published 27 May 2026

12 npm/PyPI/supply-chain threats today (2026-05-27): CVE-2026-43945 (FUXA), CVE-2026-43947 (FUXA), Laravel Lang, durabletask, AntV, node-ipc, TanStack, lightning, ...

Affects fuxaSource Reddit Cybersecurity

Compare

Mentioned vulnerabilities

CVE-2026-43947

Authoritative record:CVE-2026-43945· High 8.9

Public exploit available · CVSS 8.9 High : upgrade to 1.3.0-2706 as a priority.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 4.0 base score

8.9High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.3.0-2706

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: High
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the vulnerable system. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the vulnerable system.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade fuxa to 1.3.0-2706.

Affected software

Product	Affected	Fixed in
npmfuxa`pkg:npm/fuxa`Other threats	Affected <1.3.0-2706	Fixed in 1.3.0-2706
Packagistlaravel/lang`pkg:composer/laravel/lang`Other threats	Affected *	Fixed in–
PyPIdurabletask`pkg:pypi/durabletask`Other threats	Affected *	Fixed in–
npmantv`pkg:npm/antv`Other threats	Affected *	Fixed in–
npmnode-ipc`pkg:npm/node-ipc`Other threats	Affected *	Fixed in–
npmtanstack`pkg:npm/tanstack`Other threats	Affected *	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

For compromised packages such as Laravel Lang, durabletask, AntV, node-ipc, TanStack, and lightning, remove or audit installed versions and revert to known good versions or trusted sources. For yeoman-environment, upgrade to version 6.0.1 or later. For Armoli Technology Cargo Tracking System, Log4j 2.x, Langflow, and Argo CD, upgrade to patched versions or migrate as recommended. Follow vendor advisories for specific remediation steps.

Discussion

On May 27, 2026, multiple critical supply chain vulnerabilities were disclosed affecting popular packages across npm, PyPI, Composer, Cargo, Maven, and GitHub Actions ecosystems. The FUXA package is vulnerable to unauthenticated remote code execution via path manipulation and script test mode authorization bypass. Several widely used packages including Laravel Lang, durabletask, AntV, node-ipc, TanStack, and lightning have been compromised through malicious republishing or maintainer account compromises, risking credential theft and arbitrary code execution. Additional high-severity issues include authorization bypasses and deserialization vulnerabilities in other packages. Immediate remediation involves upgrading affected packages or auditing and uninstalling compromised ones as recommended. These vulnerabilities underscore ongoing risks in software supply chains and the critical importance of dependency management.

r/cybersecurity (opens in a new tab)u/Deam00n0 points0 comments

Today, May 27, 2026, we've identified 12 critical security threats across npm, PyPI, and supply-chain ecosystems. These vulnerabilities, detected in the past 24 hours, pose significant risks to software development.

#	Package / Advisory	Ecosystem	Severity	Fix
1	FUXA · CVE-2026-43945	npm	CRITICAL	Update
2	FUXA · CVE-2026-43947	npm	CRITICAL	Update
3	Laravel Lang Supply Chain Advisory	Composer	CRITICAL	Uninstall / Audit
4	`durabletask`	PyPI	CRITICAL	Uninstall / Audit
5	AntV Supply Chain Attack	npm	CRITICAL	Uninstall / Audit
6	`node-ipc`	npm	CRITICAL	Uninstall / Audit
7	TanStack Packages	npm	CRITICAL	Uninstall / Audit
8	`lightning`	PyPI	CRITICAL	Uninstall / Audit
9	FUXA · CVE-2026-43946	npm	HIGH	Update
10	`yeoman-environment` · CVE-2026-42089	npm	HIGH	6.0.1
11	Armoli Technology Cargo Tracking System · CVE-2023-2065	Cargo	HIGH	Update
12	Log4j 1.x JMSSink · CVE-2022-23302	Maven	HIGH	Migrate away / Update
13	Langflow · CVE-2025-34291	PyPI	HIGH	Update
14	Argo CD · CVE-2022-24348	GitHub Actions	HIGH	Upgrade

FUXA Vulnerable to Pre-auth RCE via Path Manipulation & Configuration Injection

Ecosystem: npm CVE: CVE-2026-43945 Severity: CRITICAL This vulnerability chain in FUXA (v.1.3.0-2706) allows unauthenticated remote attackers to achieve Full Remote Code Execution (RCE) as root, even in secure configurations. Action Required: Upgrade to a version that addresses this vulnerability. Source

FUXA Vulnerable to Unauthenticated Remote Code Execution via Script Test Mode Authorization Bypass

Ecosystem: npm CVE: CVE-2026-43947 Severity: CRITICAL A vulnerability in FUXA's POST /api/runscript endpoint allows unauthenticated attackers to execute arbitrary code via test mode if a server-side script exists. Action Required: Upgrade to a version that addresses this vulnerability. Source

Laravel Lang Supply Chain Advisory

Ecosystem: Composer Severity: CRITICAL Hundreds of historical Laravel Lang Packagist releases were republished with malicious code, risking credential theft and secret exfiltration. Action Required: Remove or audit any Laravel Lang packages installed from Packagist. Use trusted sources for dependencies. Source

The AntV Supply Chain Campaign Expands: Microsoft's durabletask PyPI Package Compromised

Ecosystem: PyPI Severity: CRITICAL The AntV supply chain attack campaign has compromised durabletask, a Microsoft-associated Python package on PyPI, potentially exposing users to malicious code. Action Required: Remove or audit any durabletask packages installed from PyPI. Use trusted sources for dependencies. Source

Mini Shai-Hulud Hits AntV: 300+ Malicious npm Packages Published via Compromised Maintainer Account

Ecosystem: npm Severity: CRITICAL A compromised npm maintainer account led to the automated release of over 300 malicious package versions in the AntV ecosystem as part of the Mini Shai-Hulud campaign. Action Required: Audit your dependencies for any AntV packages. Remove or revert to known good versions. Source

Malicious node-ipc versions published to npm in suspected maintainer account compromise

Ecosystem: npm Severity: CRITICAL Multiple malicious versions of the popular node-ipc npm package were published to the npm registry, posing a risk to users. Action Required: Audit your dependencies for node-ipc. Remove or revert to known good versions. Source

TanStack Npm Packages Compromised Inside The Mini Shai Hulud Supply Chain Attack

Ecosystem: npm Severity: CRITICAL The Mini Shai-Hulud worm compromised 84 npm package artifacts across 42 /* packages, chaining GitHub Actions vulnerabilities to achieve supply chain attacks with valid SLSA Build Level 3 attestations. Action Required: Audit your dependencies for u/tanstack* packages. Remove or revert to known good versions. Source

lightning PyPI Compromise: A Bun-Based Credential Stealer in Python

Ecosystem: PyPI Severity: CRITICAL A malicious release of the lightning PyPI package includes a credential-stealing Bun payload that runs on import, potentially compromising user credentials. Action Required: Remove or audit any lightning packages installed from PyPI. Use trusted sources for dependencies. Source

FUXA has an unauthenticated arbitrary tag value disclosure via /api/getTagValue

Ecosystem: npm CVE: CVE-2026-43946 Severity: HIGH An authorization bypass in FUXA's /api/getTagValue endpoint allows unauthenticated access to tag values when the referenced script does not exist. Action Required: Upgrade to a version that addresses this vulnerability. Source

yeoman-environment Vulnerable to Arbitrary Package Installation without User Confirmation

Ecosystem: npm CVE: CVE-2026-42089 Severity: HIGH yeoman-environment versions >= 2.9.0 and < 6.0.1 can install arbitrary packages without confirmation, leading to potential code execution during CLI bootstrap. Action Required: Upgrade to version 6.0.1 or later. Source

CVE-2023-2065 - Authorization Bypass Through User-Controlled Key vulnerability in Armoli Technology Cargo Tracking System allows Authent

Ecosystem: Cargo CVE: CVE-2023-2065 Severity: HIGH An authorization bypass vulnerability in Armoli Technology Cargo Tracking System allows for authentication abuse and bypass. Action Required: Upgrade to a version that addresses this vulnerability. Source

CVE-2022-23302 - JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write acce

Ecosystem: Maven CVE: CVE-2022-23302 Severity: HIGH Log4j 1.x's JMSSink is vulnerable to deserialization of untrusted data, potentially leading to remote code execution if configured with an attacker-accessible LDAP service. Action Required: Upgrade to Log4j 2.x or migrate away from JMSSink. Source

CVE-2025-34291 - Langflow Origin Validation Error Vulnerability

Ecosystem: PyPI CVE: CVE-2025-34291 Severity: HIGH Langflow contains an origin validation error vulnerability due to permissive CORS configuration, allowing malicious webpages to perform cross-origin requests with credentials and potentially achieve system compromise. Action Required: Upgrade to a version that addresses this vulnerability. Source

Lessons learned from the Argo CD zero-day vulnerability (CVE-2022-24348)

Ecosystem: GitHub Actions CVE: CVE-2022-24348 Severity: HIGH This vulnerability in Argo CD highlights the risks of supply chain attacks and the importance of securing CI/CD pipelines. Action Required: Upgrade Argo CD to a patched version. Source

Automated daily digest — feedback welcome. Repo: https://github.com/Deam0on/wakellm

Links cited in the discussion

https://github.com/Deam0on/wakellm

Impact

The vulnerabilities enable unauthenticated remote code execution with root privileges in FUXA, risking full system compromise. Compromised packages in Laravel Lang, durabletask, AntV, node-ipc, TanStack, and lightning expose users to malicious code execution and credential theft. Authorization bypasses and deserialization flaws in other packages increase the risk of unauthorized access and potential remote code execution. These supply chain compromises can lead to widespread impact on software projects relying on these dependencies.

References

Community reviews

Loading reviews…