# CVE-2026-3531: OpenID Connect / OAuth client - Moderately critical - Access bypass - SA-CONTRIB-2026-026


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** DRUPAL-CONTRIB-2026-026, GHSA-f2x9-px9q-jxw2

## What is CVE-2026-3531?

CVE-2026-3531 is a medium-severity vulnerability in Drupal OpenID Connect / OAuth client, published on 26 Mar 2026. 

### Official description

Authentication Bypass Using an Alternate Path or Channel vulnerability in Drupal OpenID Connect / OAuth client allows Authentication Bypass.This issue affects OpenID Connect / OAuth client: from 0.0.0 before 1.5.0.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-3531?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/openid_connect` | Packagist:https://packages.drupal.org/8 | All versions | 1.5.0 |

Products: Bojanz Openid Connect \/ Oauth Client.

## How do I fix CVE-2026-3531?

Upgrade to a fixed version.

## Is CVE-2026-3531 being exploited?

There is no known exploitation of CVE-2026-3531 in the wild and no public exploit code.

## Other vulnerabilities in Drupal OpenID Connect / OAuth client

- [CVE-2026-3530](https://insights.sbomify.com/CVE-2026-3530/): Server-side request forgery in OpenID Connect / OAuth client (medium 4.3)
- [CVE-2026-3532](https://insights.sbomify.com/CVE-2026-3532/): OpenID Connect / OAuth client - Less critical - Access bypass - SA-CONTRIB-2026-027 (medium 4.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-3531 and fix it if it is affected.

What it is: CVE-2026-3531 is a medium-severity vulnerability in Drupal OpenID Connect / OAuth client, published on 26 Mar 2026. 
Exploitation: There is no known exploitation of CVE-2026-3531 in the wild and no public exploit code.

Affected product: Drupal OpenID Connect / OAuth client. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-3531/ (Markdown: https://insights.sbomify.com/CVE-2026-3531/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-3531
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-3531
- OSV: https://osv.dev/vulnerability/CVE-2026-3531

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-3531/
Summaries are generated and may contain mistakes; the official description above is the record.