/

CVE-2026-85638

Severity:

HIGH RISK

(7.3)

Authorization Bypass (CWE-285) in Trape core/user.py

CVE-2026-85638

Deferred

Vulnerability type

Category:

Authorization Bypass

CWE:

CWE-285, CWE-639

Impact:

Unauthorized access or modification of protected resources

Severity:

HIGH RISK

(7.3)

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

A high-severity authorization weakness in jofpin Trape 2.0 allows requests that manipulate the vId or id argument to bypass intended access checks. Because the affected functionality is remotely reachable, an attacker may access or modify resources without the permissions normally required.

Affected context

The issue occurs in the core/user.py component of jofpin Trape 2.0 when authorization decisions rely on user-controlled vId or id values. Deployments are at risk where the affected endpoint is remotely reachable and does not consistently verify that the requested resource belongs to, or is authorized for, the requesting identity.

Exploit preconditions

  • Attack surface: A remotely reachable application endpoint associated with core/user.py
  • Required access: The ability to send requests to the affected functionality; valid authentication requirements may depend on deployment configuration
  • Trigger point: Processing of manipulated vId or id request arguments
  • Why exploitation is possible: Authorization checks may trust attacker-controlled identifiers without reliably enforcing ownership or permission relationships

Why this happens

The underlying bug is an authorization design weakness in which a request-supplied identifier influences access decisions without a complete server-side authorization check. This maps primarily to CWE-285: Improper Authorization and is also consistent with CWE-639: Authorization Bypass Through User-Controlled Key, where changing an object or record reference can expose functionality or data belonging to another security context.

Potential impact

  • Unauthorized users may access protected records or functionality
  • Attackers could modify or delete resources they do not own
  • Sensitive information may be disclosed across user or tenant boundaries
  • Account or application integrity could be weakened
  • Exploitation could support follow-on attacks against trusted users or services

General mitigation guidance

Mitigation generally centers on making authorization decisions independently of user-controlled object identifiers.

Common defensive patterns include:

  • Enforcing server-side, object-level authorization for every requested resource
  • Binding resource ownership and permissions to the authenticated security context
  • Avoiding reliance on client-provided identifiers as proof of entitlement
  • Applying deny-by-default authorization policies and least privilege
  • Using opaque references where appropriate, while treating them as identifiers rather than authorization controls
  • Returning consistent responses that do not disclose whether unauthorized resources exist
  • Adding authorization regression tests for cross-user and cross-tenant access attempts

How teams detect issues like this

Organizations can identify similar weaknesses through:

  • Static analysis rules that flag authorization decisions based directly on request parameters
  • Code review checks for missing object-level authorization near database lookups or update operations
  • Tests that substitute identifiers belonging to other users, roles, or tenants
  • Runtime monitoring for repeated requests that enumerate or vary resource identifiers
  • Policy enforcement requiring explicit authorization checks at service or controller boundaries
  • Automated security review tools that correlate user-controlled identifiers with protected-resource access

Sources

SourceLink
github.comgithub.com/jofpin/trape/
github.comgithub.com/jofpin/trape/issues/407
vuldb.comvuldb.com/cve/CVE-2026-85638
vuldb.comvuldb.com/submit/895139
vuldb.comvuldb.com/vuln/398786
vuldb.comvuldb.com/vuln/398786/cti

Frequently asked

questions

Yes. The description indicates that the affected functionality can be reached remotely, although successful exploitation still depends on the endpoint being exposed and any applicable authentication or network controls.

Not necessarily. The decisive requirement is access to the affected request path; whether authentication is required depends on the deployment and endpoint configuration.

Perform a server-side authorization check for every referenced resource, using the authenticated identity and its permissions rather than trusting vId or id values supplied by the client.

Apply deny-by-default access policies, centralize authorization logic, test cross-user and cross-tenant object access, and monitor for identifier enumeration or unusual access patterns.

Find out what's already
exploitable in your codebase.