Skip to main content
VulnerabilityPublished Updated

CVE-2026-42298: gitroomhq postiz-app · Code Injection

Affects gitroomhq postiz-appSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 10.0 Critical.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
gitroomhqpostiz-appAffected
  • =< da448012dd87e94944cbe83a38e7fd023269ec46
Fixed in–

AI-suggested

This vulnerability has been patched in commit da44801. Users should update postiz-app to versions including this commit or later to remediate the issue. Since this is not a cloud service, manual patching is required. There is no vendor advisory content contradicting this; therefore, applying the official fix is the recommended mitigation.

Description

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 GITHUB_TOKEN (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.

References

Community reviews

Loading reviews…