Authenticated cross-user metadata disclosure via missing ownership checks
Published Aug 18, 2026 · Updated Aug 19, 2026
Authorization bypass in Kurrier before 1.2.4 allows remote authenticated users to read other users' webhook and identity metadata via API requests. The GET and list handlers in apps/worker/server/routes/api/kurrier/webhooks/[id].get.ts, apps/worker/server/routes/api/kurrier/webhooks/index.get.ts, apps/worker/server/routes/api/kurrier/identities/[id].get.ts, and apps/worker/server/routes/api/kurrier/identities/index.get.ts accepted a valid API key but fetched records by supplied IDs or returned lists without constraining queries to the caller's ownerId. A valid API key is required, anonymous and invalid-key requests are rejected, and the exposed operations are bounded to cross-user enumeration and metadata disclosure rather than modification.
Summary
What happened
Authorization bypass in Kurrier before 1.2.4 allows remote authenticated users to read other users' webhook and identity metadata via API requests. The GET and list handlers in apps/worker/server/routes/api/kurrier/webhooks/[id].get.ts, apps/worker/server/routes/api/kurrier/webhooks/index.get.ts, apps/worker/server/routes/api/kurrier/identities/[id].get.ts, and apps/worker/server/routes/api/kurrier/identities/index.get.ts accepted a valid API key but fetched records by supplied IDs or returned lists without constraining queries to the caller's ownerId. A valid API key is required, anonymous and invalid-key requests are rejected, and the exposed operations are bounded to cross-user enumeration and metadata disclosure rather than modification.
The record
- CVE
- CVE-2026-50167
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Kurrier
- Product
- Kurrier
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.2.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo