Habr•November 18, 2026•🇷🇺Translated from Russian

DPoP Enforcement Failure Allows Bearer Token Bypass in redb.Identity OpenID Server

redb.Identity, an open-source OAuth 2.1 / OpenID Connect server for .NET, contained a flaw that allowed DPoP-bound access tokens to be used without any proof-of-possession on two internal endpoints.

The vulnerability, tracked as GHSA-vmj2-8phj-mfxf and rated CWE-287 with a CVSS 3.1 score of 7.4 (High), existed in redb.Identity.Core versions 1.0.1 through 4.6.1 when the DPoP feature was enabled.

What was broken

When DPoP is active, the server issues tokens containing a cnf.jkt claim that binds the token to a client key. Every subsequent request must include a signed DPoP proof containing the HTTP method, target URI, timestamp, jti, and the hash of the token itself. On the affected endpoints /connect/userinfo and the management API /api/v1/identity/... (including SCIM), the server read only the Bearer scheme and ignored the DPoP header entirely. Consequently, a stolen token could be presented without any proof or private key and would still be accepted.

Resource servers using redb.Identity.Resource.Dpop were not affected because they always performed the proof validation.

Why automated tests missed it

The project runs approximately 2,000 tests on PostgreSQL, SQL Server and SQLite. A test named “userinfo accepts token bound via DPoP” sent a valid token with both Bearer and DPoP headers and asserted a 200 response. Because the endpoint never examined the DPoP header, the same request would have succeeded even without the header, so the test passed while the security property remained broken.

An earlier migration to OpenIddict 7 had temporarily caused 500 errors for jkt-bound tokens; developers added a workaround that disabled cnf checking and documented that “DPoP proof is validated by Identity itself.” That assumption proved false for the two endpoints in question.

Discovery and remediation timeline

  • 4 November – Private report received from researcher Rathnadeepan (GitHub HotWater-015).
  • Same day – Source-code confirmation; range extended back to 1.0.1 after tests on older commits.
  • 23:06 same day – First failing tests covering missing proofs, wrong keys, replayed jti, mismatched method/URI, and other negative cases.
  • 23:33 – Patch committed; all 2,007 tests green on three databases.
  • 5 November – Version 4.6.2 released to NuGet.

After the fix, bound tokens are accepted on HTTP endpoints only when presented with scheme DPoP and a valid proof. gRPC and SOAP management channels now reject bound tokens because they cannot carry the required proof.

Disclosure and lessons

The advisory was published on 15 November under its GHSA identifier after the reporter consented; no CVE number had been assigned despite two requests to GitHub. The project now requires negative tests for every protected endpoint and runs a full DPoP demo scenario against every release candidate.

Related articles

Securitylab•Vulnerabilities & Exploits

Managing Bug Bounty Programs: Handling Report Overload, Duplicates, and AI-Generated Submissions

Launching a bug bounty program is only the beginning; the real challenge lies in managing the influx of reports, filtering duplicates and AI-generated noise, and ensuring vulnerabilities are actually fixed. Standoff Bug Bounty recommends starting with private programs limited to 30-50 researchers to build internal processes before scaling. Companies like Flavau developed custom DevSecOps consoles that cut report triage time by a factor of 10 by automating duplicate detection and assignee assignment. The platform introduced neural slop windows that limit submissions based on researcher quality history, addressing the surge in AI-generated invalid reports observed in spring 2026. Fixed response timelines, clear ownership roles, and prioritized remediation of critical issues help maintain program effectiveness. Google’s decision to pause its OSS VRP in October 2026 due to automated report floods highlights broader industry concerns, yet experts maintain that human-driven independent validation remains essential. Key success metrics include reduced risk from fixed high-severity issues, lower average payout costs, and improved cross-team communication between security and development.

Habr•Vulnerabilities & Exploits

Researcher Bypasses Safe Exam Browser Checks in Moodle Using MITM Proxy and Canonical Config Key Hash

A detailed technical write-up describes how a student bypassed the proprietary Safe Exam Browser requirement for Moodle quizzes by reverse-engineering the single-header authentication mechanism. The bypass relies on fetching the public SEB configuration XML from the open endpoint, computing a canonical SHA256 hash known as ConfigKey, and injecting the resulting X-SafeExamBrowser-ConfigKeyHash header via mitmproxy. Moodle caches a successful check inside the PHP session, allowing all subsequent requests to be made from a normal browser without further header manipulation. Two implementations were created: a headless Python client for full automation of quizzes and a transparent mitmproxy addon that lets a user continue interacting with the test manually. The author also handled edge cases such as crossword OCR with Tesseract, dynamic qubaid and sequencecheck values on retakes, and audio listening sections. The resulting scores reached 772 out of 780 points, placing the account 22nd out of 372 students. The full code, including configkey.py, mitm_addon.py and unit tests, has been published under CC BY-NC-SA 4.0.

Security NEXT•Vulnerabilities & Exploits

Oracle Releases 655 Security Patches in November 2026 Critical Update

Oracle has published its November 2026 Critical Security Patch Update, delivering a total of 655 patches that address vulnerabilities across a wide range of products. The update resolves 640 unique CVEs after accounting for duplicates and supplements the regular quarterly Critical Patch Update. Affected products include Oracle Database Server, Oracle Java SE, MySQL Server, Oracle WebLogic Server, Oracle E-Business Suite, and Oracle VM VirtualBox. Among the fixes, Oracle Hyperion accounts for the largest share with 267 patches, followed by Oracle Supply Chain with 74 and both Oracle Fusion Middleware and Oracle E-Business Suite with 71 each. Of the vulnerabilities patched, 311 carry a CVSSv3.1 base score of 7.0 or higher, including 62 rated 9.0 or above, while 303 can be exploited remotely.

Security NEXT•Vulnerabilities & Exploits

Mozilla Releases Firefox 160.0.1 to Address Two High-Severity Vulnerabilities

Mozilla Foundation has issued Firefox 160.0.1 to resolve two vulnerabilities rated High severity. The update addresses a Use After Free flaw in the Audio/Video:Playback component and a boundary condition issue in the Graphics:CanvasWebGL component on Android. Both vulnerabilities were disclosed in a security advisory published on November 17, 2026. The first issue, tracked as CVE-2026-130021, involves improper memory handling during audio and video playback that could lead to exploitation. The second vulnerability, CVE-2026-130020, affects graphics processing on Android and may allow privilege escalation. Users are advised to apply the update promptly to mitigate potential risks.