CVE-2026-115932 — Path traversal in post media lets any registered user read server files
When a post is published, Postiz treats a media path that is not a web address as a file on the server's disk, but it does not check that the file lies inside the upload directory. A registered user can store a crafted media path with a post, get it past the checks that normally restrict it, and have the publishing worker read an arbitrary file and send it as an attachment to a Discord server the user controls. The same unconfined reads can be reached through two further routes. One tells the caller whether a file exists and can exhaust the backend's memory, the other delivers the file the same way as the main route. Self-registration is open by default, so the attacker needs no existing account.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+6
- Technical severity (critical)+10
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Gitroomhq Postiz-app).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (file handling), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Gitroomhq | Postiz-app | ≥ 2.23.0 and < 2.25.3 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 9.6 | CVSS 3.1 | Critical | 3.1 | 5.8 | 4cdc9741-f887-419a-a2fd-acbbd2729276 via NIST National Vulnerability Database |
| 9.6 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.6 | CVSS 3.1 | Critical | — | — | postiz via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N (score shown at the top: 4cdc9741-f887-419a-a2fd-acbbd2729276) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 25, 2026 → Oct 29, 2026 · 5 reading(s) · max 0.43%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor file creation in web directories and paths with traversal sequences (../).
Timeline
What happened to this CVE, newest first.
- 2026
- Source status changed · Received → Deferred
- Source status changed · Published → Received
- Record published
- CVSS changed · 9.6
- Source status changed · → Published
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 26, 2026 – Oct 26, 2026
- 1× Official description updated · Oct 24, 2026 – Oct 24, 2026
References
6 on the record
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-115933 Forged signed tokens let any registered user take over other users and organizations 5d
- Critical CVE-2026-115931 Arbitrary file read and backend crash through unrestricted provider method calls 6d
- Medium CVE-2026-107761 Channel tokens and organization API key exposed in API responses 18d
- Critical CVE-2026-94456 Unauthenticated recovery of the Math.random() state behind OAuth tokens, authorization codes, client secrets and organization API keys Sep 22, 2026
- High CVE-2026-94455 Unauthenticated /enterprise/create-user mints lifetime top-tier organizations and discloses their API key Sep 22, 2026
- Critical CVE-2026-19264 Unauthenticated arbitrary file read via /uploads path traversal (URL-encoded separators) leading to instance takeover Aug 7, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-115932 is "Path traversal in post media lets any registered user read server files", rated Critical. It affects Postiz-app (Gitroomhq); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.6 describes technical severity. EPSS 0.43% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.