cve.bz

CVE-2026-134824 Nektos act 0.2.92 before 0.2.98 Link Following via .actrc --eventpath

6.8 mediumFix available

Medium (6.8) in nektos act.

On this page
Nektos act 0.2.92 before 0.2.98 contains a link following vulnerability that allows malicious repositories to read host files by setting --eventpath in an untrusted project .actrc to a symlink. Attackers can commit an event.json symlink pointing to files like ~/.ssh/id_rsa, which act copies into the job container as GITHUB_EVENT_PATH for workflow steps to exfiltrate.

Severity

CVSS 4.0

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

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
CWE
CWE-59 Improper Link Resolution Before File Access (Link Following)
OWASP Top 10
A01:2025 Broken Access Control
Published
Assigned by
VulnCheck (CNA)
NVD analysis
Not in the NVD yet
Record from
the CVE List, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-134824 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-134824?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-134824?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-134824 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
nektos actfrom 0.2.92 before 0.2.98

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-132 Symlink Attack Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON