/

CVE-2026-19264

Severity:

CRITICAL RISK

(9.8)

Path Traversal (CWE-22) in Postiz Media File Route

CVE-2026-19264

Deferred

Vulnerability type

Category:

Path Traversal

CWE:

CWE-22

Impact:

Unauthenticated Arbitrary File Read and Account Takeover

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Postiz contains an unauthenticated path traversal vulnerability in the route that serves locally stored media. An attacker may read files accessible to the application process, potentially exposing signing keys and other secrets that can enable administrator session forgery.

Affected context

The issue occurs in Postiz deployments where a media-serving route combines URL-supplied path segments with an upload directory without normalizing the resulting path or enforcing confinement to that directory. URL-encoded separators can bypass routing-time dot-segment handling and be decoded later by the filesystem operation, allowing traversal when the route is reachable without authentication.

Exploit preconditions

  • Attack surface: Unauthenticated HTTP media-serving route
  • Required access: Network access to the exposed Postiz instance; no account is generally required
  • Trigger point: Filesystem access performed after URL path decoding in the route handler
  • Why exploitation is possible: User-controlled path components are joined to the upload directory without canonicalization and a boundary check

Why this happens

The vulnerability results from treating URL-derived path segments as trusted filesystem paths. The route does not normalize the combined path or verify that the resolved location remains within the intended upload directory, while decoding behavior allows traversal syntax to reach the filesystem layer after routing. This maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory, commonly known as path traversal.

Potential impact

  • An attacker may read arbitrary files accessible to the application process
  • Process environment data could expose JWT signing secrets, database credentials, and provider or billing secrets
  • Attackers could forge valid sessions, potentially including administrator sessions
  • Sensitive application data and connected services could be compromised
  • The application could experience unauthorized account access and broader data exposure

General mitigation guidance

Mitigation typically focuses on treating all path components as untrusted and enforcing a strong filesystem boundary.

Common defensive patterns include:

  • Resolve candidate paths canonically before access and verify they remain beneath the intended media directory
  • Prefer opaque file identifiers or server-managed mappings instead of accepting filesystem paths from clients
  • Reject traversal syntax, encoded separators, and unexpected path formats as defense-in-depth controls
  • Require authentication and authorization for media access where public delivery is not necessary
  • Store application secrets outside broadly readable process environments where practical, and apply least privilege to the application process
  • Use short-lived, narrowly scoped session tokens and rotate exposed credentials when compromise is suspected

How teams detect issues like this

Organizations commonly detect path traversal risks through:

  • Static analysis rules for filesystem APIs receiving URL parameters or other request-derived values
  • Code review checks for path joining without canonicalization and directory-boundary validation
  • Dynamic testing with encoded separators, traversal markers, and alternate path representations
  • Web application firewall or gateway policies that flag suspicious encoded path patterns
  • Monitoring for unexpected access to environment files, credential stores, system metadata, or paths outside the media directory

Automated security review tools can help identify request-to-filesystem data flows, but findings should be validated against the application's routing and decoding behavior.

Sources

SourceLink
gadvisory.orggadvisory.org/advisories/PSA-2026-TH12B7
github.comgithub.com/gitroomhq/postiz-app/commit/7936062
github.comgithub.com/gitroomhq/postiz-app/releases/tag/v2.22.1

Frequently asked

questions

Yes. The affected route is reachable over the network without authentication when the Postiz instance is exposed, so an attacker may not need an existing account.

Network access to the vulnerable media-serving endpoint is generally sufficient. The attacker does not need write access to the server filesystem because the issue reads files already accessible to the application process.

Treat requested media names as untrusted identifiers, resolve paths canonically, and enforce that every resolved path remains inside the intended media directory. Authentication and authorization should also be applied when media does not need to be public.

Use centralized safe-path utilities, review all request-to-filesystem data flows, test encoded and alternate path representations, minimize process privileges, and keep session and credential-management controls resilient if application secrets are exposed.

Find out what's already
exploitable in your codebase.