CVE-2026-42298Network attack vector

Repository takeover via untrusted pull-request Dockerfile

Published May 8, 2026 · Updated May 8, 2026

Code injection in Postiz before commit da44801 allows remote attackers to execute code in GitHub Actions and obtain a write-all token. The pull_request_target workflow checks out a fork's head revision, then runs docker build against its attacker-controlled Dockerfile.dev while the job carries write-all permissions. Opening or updating a forked pull request is sufficient; the token permits full read-write control of the repository, including commits and releases.

CVSS severity10.0
Critical
EPSS probability0.50%
Next 30 days · Sep 16, 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.

Book a demo

Summary

What happened

Code injection in Postiz before commit da44801 allows remote attackers to execute code in GitHub Actions and obtain a write-all token. The pull_request_target workflow checks out a fork's head revision, then runs docker build against its attacker-controlled Dockerfile.dev while the job carries write-all permissions. Opening or updating a forked pull request is sufficient; the token permits full read-write control of the repository, including commits and releases.

The record

CVE
CVE-2026-42298
Published
May 8, 2026
Updated
May 8, 2026
Vendor
GitroomHQ
Product
Postiz
Classifications
CWE-94, T1195.001
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 8, 2026CVE publishedPublication date reported by the CVE source.
  2. May 8, 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?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< da448012dd87e94944cbe83a38e7fd023269ec46

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

GitroomHQ · Postizversion=< da448012dd87e94944cbe83a38e7fd023269ec46

Published CVSS scores

9.8NIST NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
10.0GitHubCVSS: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.

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

No observations available

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

Weakness, pattern, technique

CWE-94Improper Control of Generation of Code ('Code Injection')
T1195.001Compromise Software Dependencies and Development Tools

Public exploit references

No public exploit references are available in this record.

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

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo