vciy

CVE-2025-67642

INDEX BUILT · 2026-10-18

No source can show you its own past. This one can.

Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.

Jenkins HashiCorp Vault Plugin 371.v884a_4dd60fb_6 and earlier does not set the appropriate context for Vault credentials lookup, allowing attackers…

CVE-2025-676424 of 4 sources documented this
2

rank 2 = 0 + 0 + 0 + 2 + 0

rank@v1 · backlog

Someone is already using it

CISA KEV catalog · public proof-of-concept · FIRST EPSS

EPSS 0.00231  ·  without this subject the record ranks 2

What it costs you if it fires

NVD CVSS base score, then the CNA's own

no CVSS held by anyone  ·  without this subject the record ranks 2

It is getting worse, not staying still

FIRST EPSS series, rescorings and bad loads removed

no persisting rise in 365 days  ·  without this subject the record ranks 2

How much of the world it touches

NVD CPE configurations

1 product in the CPE ranges  ·  without this subject the record ranks 0

Someone else already set the date

CISA KEV remediation due date

no CISA due date  ·  without this subject the record ranks 2

Hindsight · the state

0.00231EPSSNOT IN KEVas of 2026-10-18
Severitynot scored
Harmnot stated
Exploitationnone in held sources
Defenseno fix version held
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-12-11, 268 days at 0.00, as of 2026-09-05. arc-rules@v1

Foresight · where to check next

No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.

Color is a claim, not decoration:the hostile worldthe defenseno signal

Running Jenkins HashiCorp Vault Plugin? Check your version

A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.

Watch this record

Matches your own product list against every record this index holds, and tells you when one of them moves.

What counts as a move

Watch Jenkins HashiCorp Vault Plugin

Set up a watchlist (free with an account: one stack of three products)

Record your call

Keep your verdict, your reason and the evidence together. The record takes its date when you save it.

Patch by…

Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.

Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.

Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.

Harm, if it fires from the vector and the weakness

Written for the ticket you're about to file.

ReachNo CVSS vector in held sources, so no reach or impact can be stated.
Weakness classCWE-282 Improper Ownership Managementreceipt
Published consequencesCWE-282: Access Control: Gain Privileges or Assume Identitycwe-consequences@4.20

CISA KEV & Federal Remediation Deadline from the record and CISA

The fix, and how long it's been waiting.

Fixed inNo fix version in held sources, as the index stood on 5 Sep 2026.
Patch available sinceNo dated patch-availability record in held sources. The index holds reference URLs without dates and only the current revision of the CVE record, so the day a fix first existed cannot be derived. Only the versions it landed in.
BOD 26-04 deadlineIf the system is reachable from the internet: 14 days. If not: fix at the next system upgrade.derived
Show full BOD 26-04 deadline

CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table

Exploit Status & Known PoCs a ladder, not a score

Current rung: Nothing observed in held sources.

  • RUNG 1Nothing observed in held sources
  • RUNG 2Proof-of-concept published
  • RUNG 3Exploited in the wild · CISA KEV listed
  • RUNG 4Ransomware campaign use known

Authority who says so

Exploit probability0.00231 · top 87% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byjenkinsreceipt
Recorded changes14 · last 18 Oct 2026derived

Affected & Fixed Versions as published

Affected productJenkins Project Jenkins HashiCorp Vault Pluginreceipt
Published rangesjenkins hashicorp vault <= 371.v884a_4dd60fb_6receipt

A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.

Did this affect your environment?Answering needs an account.

What it is stated by the CNA

Jenkins HashiCorp Vault Plugin 371.v884a_4dd60fb_6 and earlier does not set the appropriate context for Vault credentials lookup, allowing attackers with Item/Configure permission to access and potentially capture Vault credentials they are not entitled to. receipt

NVD's analysis a second authority

weakness
CWE-282
affected versions
jenkins hashicorp vault <= 371.v884a_4dd60fb_6
also scored by
4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

check it yourself jenkins.io receipt

Movement the material steps

11 Dec 20250.00025
15 Jun 20260.00194 · scoring model v2026.06.15
5 Sep 20260.00231

This score more than doubled inside 72 hours. Both observations are in the full history below.

Show all 14 observations
11 Dec 20250.00025
16 Dec 20250.00028
18 Dec 20250.0011
11 Jan 20260.00126
16 Feb 20260.00147
11 Apr 20260.00179
8 May 20260.00111
9 May 20260.00106
20 May 20260.00126
15 Jun 20260.00194
9 Jul 20260.00202
29 Jul 20260.00206
7 Aug 20260.00226
5 Sep 20260.00231

14 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt

The full biography

EPSS 0.00231Published2025-12-10Index as of2026-09-05

Exploit probability more than doubled between 2025-12-16 and 2025-12-18 (0.00028 → 0.0011) and the record had been public for 8 months when this index was last written.

Published 2025-12-10 receipt · Index as of 2026-09-05 derived

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2025-67642.

What usually comes next

Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.

Everything on this page is free. Public data. Withholding it protects nothing.