/

CVE-2026-92753

Severity:

HIGH RISK

(7.1)

Authorization Bypass (CWE-862) in PatrowlManager APIs

CVE-2026-92753

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-862

Impact:

Unauthorized access, modification, and deletion of other users' events and alerts

Severity:

HIGH RISK

(7.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

PatrowlManager through version 1.8.4 contains an authorization bypass in its events and alerts API endpoints because ownership checks are not consistently enforced. An authenticated attacker may read platform event history, delete arbitrary events, or modify alerts belonging to other users.

Affected context

The vulnerability occurs in deployments of PatrowlManager through 1.8.4 where authenticated requests can access the events or alerts API endpoints without effective ownership filtering. Risk depends on the exposed API surface, the permissions granted to authenticated users, and whether event or alert records are shared across tenants or user accounts.

Exploit preconditions

  • Attack surface: Events and alerts API endpoints
  • Required access: A valid authenticated account capable of sending requests to the affected endpoints
  • Trigger point: API operations that retrieve event history, delete events, or modify alerts
  • Why exploitation is possible: The endpoints do not reliably constrain records by their owning user or authorized scope

Why this happens

The underlying flaw is an authorization design error in which endpoint-level authentication is treated as sufficient without applying object-level ownership or scope checks. This allows an authenticated principal to operate on records outside the principal's permitted set, mapping to CWE-862, Missing Authorization. The insecure pattern is accepting a resource identifier from a request without independently verifying that the requested operation is authorized for that specific resource.

Potential impact

  • An attacker may read platform-wide event history
  • An attacker could delete events owned by other users
  • An attacker may modify alerts belonging to other users
  • Security monitoring and incident-response records could be altered or removed
  • Organizations could experience data exposure, integrity loss, or reduced auditability

General mitigation guidance

Mitigation typically focuses on enforcing object-level authorization for every

event and alert operation.

Common defensive patterns include:

  • Applying ownership, tenant, and role checks at the service or data-access layer
  • Deriving the authorized subject and scope from the authenticated identity rather than request-controlled fields
  • Using secure-by-default API policies that deny access unless resource authorization is explicitly established
  • Separating read, update, and delete permissions and granting only the minimum required privileges
  • Testing authorization decisions for cross-user and cross-tenant access
  • Preserving audit records through tamper-resistant logging and controlled administrative workflows

How teams detect issues like this

Organizations commonly detect authorization bypass risks through:

  • Static analysis and code review checks for database queries that retrieve records without ownership or tenant predicates
  • Review of controller and service methods for resource identifiers accepted without a subsequent authorization decision
  • Policy tests that exercise each endpoint with resources belonging to other users or tenants
  • API gateway and application policies requiring explicit scopes for read, update, and delete operations
  • Monitoring for unusual cross-account access, bulk event deletion, or alert changes by accounts without corresponding roles

Automated security review tools may help identify missing object-level authorization patterns, but endpoint-specific tests remain important.

Sources

SourceLink
github.comgithub.com/Patrowl/PatrowlManager
github.comgithub.com/Patrowl/PatrowlManager/blob/1.8.4/events/apis.py#L15-L60
github.comgithub.com/Patrowl/PatrowlManager/issues/474
vulncheck.comvulncheck.com/advisories/patrowlmanager-through-1.8.4-authorization-bypass-via-events-api

Frequently asked

questions

It may be exploitable remotely when the affected events and alerts APIs are

reachable by an authenticated user. Exploitation still depends on deployment

exposure and the account's ability to invoke the endpoints.

The attacker generally needs a valid authenticated account and access to the

affected API operations. The account may not need administrative privileges if

ownership checks are missing.

Enforce object-level authorization for every requested resource and operation,

using the authenticated identity, tenant, role, and intended action to make

the decision before reading or changing data.

Use deny-by-default authorization policies, centralize ownership checks, apply

least privilege, and include cross-user and cross-tenant authorization tests

in development and security-review workflows.

Find out what's already
exploitable in your codebase.