# CVE-2026-70437: Information disclosure in Jenkins Webhook Secret Credentials Provider Plugin

> Attackers can statistically recover webhook bearer tokens due to non-constant-time comparison, potentially bypassing authentication in Jenkins.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2026
- **Updated:** 6 Aug 2026
- **Also known as:** GHSA-298v-p382-mwvw

## What is CVE-2026-70437?

CVE-2026-70437 is a low-severity vulnerability in Jenkins Webhook Secret Credentials Provider Plugin, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jenkins Webhook Secret Credentials Provider Plugin 16.v0cfa_f0215cf5 and earlier does not use a constant-time comparison function when checking whether the provided and expected webhook bearer token are equal, potentially allowing attackers to use statistical methods to obtain a valid webhook bearer token.

Weakness: CWE-208 (Observable Timing Discrepancy)

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


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

No fix has been published for CVE-2026-70437 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-70437 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-70437 is a low-severity vulnerability in Jenkins Webhook Secret Credentials Provider Plugin, published on 5 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-70437 in the wild and no public exploit code.

Affected product: Jenkins Webhook Secret Credentials Provider Plugin. 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-70437/ (Markdown: https://insights.sbomify.com/CVE-2026-70437/index.md)
```

## Sources

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

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