CVE-2026-42298: Postiz: Arbitrary Code Execution and Token Exfiltration in pr-docker-build.yml via untrusted Dockerfile.dev
Postiz is an AI social media scheduling tool. Prior to commit da44801, a "Pwn Request" vulnerability in the Build and Publish PR Docker Image workflow (.github/workflows/pr-docker-build.yml) allows any unauthenticated user to execute arbitrary code during the Docker build process and exfiltrate a highly privileged GITHUBTOKEN (write-all permissions). This can be achieved simply by opening a Pull Request from a fork with a maliciously modified Dockerfile.dev. This issue has been patched via commit da44801.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Postiz (Build and Publish PR Docker Image workflow: .github/workflows/pr-docker-build.yml)to a version that resolves this vulnerability.Patch da44801
Event History
Frequently Asked Questions
What is the severity of CVE-2026-42298?
CVE-2026-42298 is classified as a critical vulnerability due to its potential for arbitrary code execution and token exfiltration.
How do I fix CVE-2026-42298?
To mitigate CVE-2026-42298, update your Postiz application to version da44801 or later as it addresses this vulnerability.
What are the risks associated with CVE-2026-42298?
CVE-2026-42298 exposes users to the risk of arbitrary code execution and unauthorized access to sensitive tokens.
Which versions of Postiz are affected by CVE-2026-42298?
Postiz versions prior to da44801 are affected by CVE-2026-42298.
What is the context of the CVE-2026-42298 vulnerability?
CVE-2026-42298 arises from untrusted Dockerfile.dev in the pr-docker-build.yml workflow used by Postiz, allowing for exploitation during Docker image building.