CVE-2026-107761

Channel tokens and organization API key exposed in API responses

  • Medium 5.3

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.

Key facts

Published
11 Oct 2026
Last changed
15 Oct 2026
Assigned by
postiz
EPSS
0.283% likely to be exploited in the next 30 days, higher than 21.155% of CVEs (scores for 18 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 5.3CVSS 4.0, Mediumfrom the CNA (postiz)CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:L/SI:L/SA:N

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

A third-party OAuth app permitted to delete a channel obtains that channel's social platform access and refresh tokens and can act on the connected account outside Postiz. (CNA impact statement)

An organization member without the admin role obtains the organization API key and can use the public API on behalf of the organization. (CNA impact statement)

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
GitroomHQpostiz-app
  • Default status: unaffected
  • 0 up to but excluding 2.25.1 (affected)

Timeline

  1. 1 Oct 2026 Postiz has discovered the vulnerability.
  2. 8 Oct 2026 Postiz has developed and verified a patch.
  3. 11 Oct 2026 Postiz has created the release and published the advisory.
  4. 11 Oct 2026 Published

Weakness

References