Summaryinfo

A vulnerability, which was classified as critical, was found in nektos act up to 0.2.85. This issue affects some unknown processing of the component Docker Container Handler. Such manipulation leads to authorization. This vulnerability is traded as CVE-2026-34042. The attack may be launched remotely. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, has been found in nektos act up to 0.2.85. Affected by this issue is some unknown functionality of the component Docker Container Handler. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Impacted is confidentiality, integrity, and availability. CVE summarizes:

act is a project which allows for local running of github actions. Prior to version 0.2.86, act's built in actions/cache server listens to connections on all interfaces and allows anyone who can connect to it including someone anywhere on the internet to create caches with arbitrary keys and retrieve all existing caches. If they can predict which cache keys will be used by local actions, they can create malicious caches containing whatever files they please most likely allowing arbitrary remote code execution within the docker container. This issue has been patched in version 0.2.86.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-34042 since 03/25/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.

Upgrading to version 0.2.86 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch c28c27e141e8b54f9853de82f421ee09846751f7 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• nektos

Name

• act

Version

• 0.2.0
• 0.2.1
• 0.2.2
• 0.2.3
• 0.2.4
• 0.2.5
• 0.2.6
• 0.2.7
• 0.2.8
• 0.2.9
• 0.2.10
• 0.2.11
• 0.2.12
• 0.2.13
• 0.2.14
• 0.2.15
• 0.2.16
• 0.2.17
• 0.2.18
• 0.2.19
• 0.2.20
• 0.2.21
• 0.2.22
• 0.2.23
• 0.2.24
• 0.2.25
• 0.2.26
• 0.2.27
• 0.2.28
• 0.2.29
• 0.2.30
• 0.2.31
• 0.2.32
• 0.2.33
• 0.2.34
• 0.2.35
• 0.2.36
• 0.2.37
• 0.2.38
• 0.2.39
• 0.2.40
• 0.2.41
• 0.2.42
• 0.2.43
• 0.2.44
• 0.2.45
• 0.2.46
• 0.2.47
• 0.2.48
• 0.2.49
• 0.2.50
• 0.2.51
• 0.2.52
• 0.2.53
• 0.2.54
• 0.2.55
• 0.2.56
• 0.2.57
• 0.2.58
• 0.2.59
• 0.2.60
• 0.2.61
• 0.2.62
• 0.2.63
• 0.2.64
• 0.2.65
• 0.2.66
• 0.2.67
• 0.2.68
• 0.2.69
• 0.2.70
• 0.2.71
• 0.2.72
• 0.2.73
• 0.2.74
• 0.2.75
• 0.2.76
• 0.2.77
• 0.2.78
• 0.2.79
• 0.2.80
• 0.2.81
• 0.2.82
• 0.2.83
• 0.2.84
• 0.2.85

License

• open-source

Website

• Product: https://github.com/nektos/act/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion