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

> Authenticated users can retrieve sensitive channel tokens and organization API keys via API responses, potentially leading to unauthorized account access.

- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-wm8w-ph5r-v9cm

## What is CVE-2026-107761?

CVE-2026-107761 is a medium-severity vulnerability in GitroomHQ postiz-app, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-213 (Exposure of Sensitive Information Due to Incompatible Policies), CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2026-107761?


## How do I fix CVE-2026-107761?

No fix has been published for CVE-2026-107761 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107761 being exploited?

There is no known exploitation of CVE-2026-107761 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107761 and fix it if it is affected.

What it is: CVE-2026-107761 is a medium-severity vulnerability in GitroomHQ postiz-app, published on 11 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107761 in the wild and no public exploit code.

Affected product: GitroomHQ postiz-app. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107761/ (Markdown: https://insights.sbomify.com/CVE-2026-107761/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107761
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107761
- OSV: https://osv.dev/vulnerability/CVE-2026-107761

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107761/
Summaries are generated and may contain mistakes; the official description above is the record.