# CVE-2026-115933: Forged signed tokens let any registered user take over other users and organizations


- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-9j6f-8rw3-93c4

## What is CVE-2026-115933?

CVE-2026-115933 is a critical vulnerability in GitroomHQ postiz-app, published on 24 Oct 2026. 

### Official description

Postiz signs its session, invitation and password reset tokens with one shared secret and without any marker of what a token is for. A route that refreshes the credentials of a browser-extension channel signed data taken from the request itself and stored the result where the requesting user can read it back. A user could therefore obtain a validly signed token containing any claims they choose, which the application accepts as a session, as an organization invitation with a chosen role, as a password reset or as an enterprise provisioning token.

A second, narrower route that creates team invitations signs extra fields from the request body in the same way.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), CWE-345 (Insufficient Verification of Data Authenticity), CWE-290 (Authentication Bypass by Spoofing)

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


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

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

## Is CVE-2026-115933 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115933 is a critical vulnerability in GitroomHQ postiz-app, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115933 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-115933/ (Markdown: https://insights.sbomify.com/CVE-2026-115933/index.md)
```

## Sources

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

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