Skip to content

Topic

OAuth 2.0 Security

A security discipline covering vulnerabilities and hardening practices in OAuth 2.0 and OpenID Connect authorization flows and token handling.

Current stories

buildOne report1 publisher

Spring Security 7.1 resource servers stop enforcing DPoP until the app calls .dPoP()

Spring Security 7.1 no longer applies DPoP verification on resource servers automatically, so upgraded apps stop enforcing it until they add .dPoP(). InfoQ's walk-through calls the failure silent and the rest of the upgrade a version bump.

Publishers:infoq.com

Reality

Evidence55
Adoption
Not scored
Hype gap+10
Incentives
Not scored
Confidence55
securityConfirmed6 publishers

Attackers are running code on BIG-IP APM boxes configured as OAuth authorization servers

F5 disclosed CVE-2026-94127 on September 22 with hotfixes and evidence of exploitation. It is a data plane heap overflow, so a locked-down management interface still leaves the system exploitable, and federal agencies had until September 25.

Perspective Coverage

6 publishers
Builder
Builder 19%
Operator
Operator 64%
Investor
Investor 17%

Reality

Evidence78
Adoption40
Hype gap+10
Incentives30
Confidence75
securityOne report1 publisher

Device code phishing collects tokens from a sign-in page that is genuinely Microsoft's

The OAuth device authorization grant was built for smart TVs and printers. Kits such as EvilTokens use it to get victims to approve an attacker's sign-in on a page that really is Microsoft's, MFA included.

Publishers:malwarebytes.com

Reality

Evidence55
Adoption20
Hype gap+12
Incentives70
Confidence55
buildOne report1 publisher

A leftover localhost callback lets Cognito hand OAuth tokens to whatever binds port 3000

Cognito validates the redirect target by matching it against the app client's allowed callback list, so a development entry nobody removed is a valid destination for an authorization code, or for the tokens themselves where implicit grant is still on.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+35
Incentives35
Confidence50
buildOne report1 publisher

authentik checked the PKCE verifier only when the request bothered to include one

One authentik CVE covers a token endpoint accepting a missing code_verifier; another, six months later, covers an authorization endpoint accepting a missing code_challenge. OpenAM's equivalent check ships switched off.

Publishers:dev.to

Reality

Evidence60
Adoption45
Hype gap+15
Incentives20
Confidence55