Medium · CVSS 5.3CVE-2026-107761

Channel tokens and organization API key exposed in API responsesCVE-2026-107761

Answer in brief

CVE-2026-107761 records a Medium severity (CVSS 5.3) vulnerability in Channel tokens and organization API key exposed in API responses. The current sources do not mark it as known exploited. The current feed maps GitroomHQ/postiz-app (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Oct 11, 2026Updated Oct 11, 2026Source checked Oct 11, 2026First seen by HOL Oct 11, 2026Material review Oct 11, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 5.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps GitroomHQ/postiz-app (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
GitroomHQ/postiz-appgeneric	>=0 <2.25.1	2.25.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for GitroomHQ/postiz-app.
Review the reported fix. Update GitroomHQ/postiz-app to 2.25.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Oct 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Oct 11, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Oct 11, 2026

Sources and claim methodology

Upstream source description

Several Postiz endpoints return the complete database row of the record they operate on instead of only the fields the client needs. Two of them include secrets the caller is not meant to receive. The public API's channel delete returns the deleted integration row, including the channel's platform access token and refresh token. A third-party OAuth app permitted to delete a channel therefore receives that channel's social platform credentials and can use them against the connected account directly, outside Postiz. `GET /user/organizations` returns each organization row, including its API key, to every member of the organization. The API key is intended for admins only, so a member with a lower role can obtain it and call the public API on behalf of the organization. Both endpoints require a valid session, API key or OAuth token and are scoped to the caller's own organization. There is no anonymous access and no cross-tenant exposure.

Quoted source text, attributed separately from HOL analysis.