CVE-2026-107761: Channel tokens and organization API key exposed in API responses

Published Oct 11, 2026
·
Updated

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.

Affected Software

1 affected component
Postiz Postiz

Event History

Oct 11, 2026
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
DescriptionWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can obtain the exposed credentials?

A caller must already have a valid session, API key, or OAuth token and is limited to their own organization. There is no anonymous or cross-tenant exposure. Any organization member can retrieve the organization API key through GET /user/organizations, while a third-party OAuth application authorized to delete a channel can receive that channel's platform access and refresh tokens.

2

What can an attacker do with the disclosed values?

A lower-role organization member can use the organization API key to call the public API on behalf of the organization. An OAuth application that deletes a channel can use the returned social-platform access and refresh tokens directly against the connected account outside of Postiz.

3

Which endpoints and actions are involved?

GET /user/organizations returns organization rows containing the API key to every member. The public API channel-delete operation returns the deleted integration row, including the channel's platform access token and refresh token.

4

Is a fixed release identified?

The provided references include the Postiz v2.25.1 release and a source-code commit, but the affected-version range is not stated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203