CVE-2026-55675Public exploitNetwork attack vector

Code execution via fork-controlled Python build hooks

Published Oct 13, 2026 · Updated Oct 13, 2026

Code execution in Salty PR-build workflows allows remote attackers to steal deployment secrets via fork-controlled Python build hooks. The .github/workflows/build-pr.yml workflow_run job checks out the fork commit recorded by trigger-pr-build.yml and runs pip install -r requirements.txt, executing untrusted setup.py or PEP 517 hooks with privileged workflow access. Exploitation requires control of fork content and a pull request that reaches the build chain; exposed deployment tokens and repository-write permissions enable follow-on compromise.

CVSS severity10.0
Critical
EPSS probability0.43%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Code execution in Salty PR-build workflows allows remote attackers to steal deployment secrets via fork-controlled Python build hooks. The .github/workflows/build-pr.yml workflow_run job checks out the fork commit recorded by trigger-pr-build.yml and runs pip install -r requirements.txt, executing untrusted setup.py or PEP 517 hooks with privileged workflow access. Exploitation requires control of fork content and a pull request that reaches the build chain; exposed deployment tokens and repository-write permissions enable follow-on compromise.

The record

CVE
CVE-2026-55675
Published
Oct 13, 2026
Updated
Oct 13, 2026
Vendor
Unknown vendor
Product
Unknown product
Classifications
CWE-1357, CWE-829, CWE-94, T1059.006
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Oct 13, 2026CVE publishedPublication date reported by the CVE source.
  2. Oct 13, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Affected buildAffected product and version details are unavailable.

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Affected products and versions are unavailable in this record.

Published CVSS scores

10.0saltyorg/docsCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-1357Reliance on Insufficiently Trustworthy Component
CWE-829Inclusion of Functionality from Untrusted Control Sphere
CWE-94Improper Control of Generation of Code ('Code Injection')
T1059.006Command and Scripting Interpreter: Python

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started