vciy

CVE-2025-27095

INDEX BUILT · 2026-09-20

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.

JumpServer has a Kubernetes Token Leak Vulnerability

CVE-2025-270954 of 4 sources documented this
15

rank 15 = 0 + 11 + 0 + 4 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00320  ·  without this subject the record ranks 15

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 4.3, from the CNA  ·  without this subject the record ranks 4

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 15

How much of the world it touches

NVD CPE configurations

2 products in the CPE ranges  ·  without this subject the record ranks 11

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$3,840over the next 30 days, if this record is yours
Movementno material movementthe record holds only daily drift and scoring model releases
Basisassumeda published average, not your estate

$3,840 = $4.99M incident cost x 0.24048551839932833 exposure x 0.0032 likelihood

udv@v1 · unaudited · wrong for you until you say what you run

$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.

Hindsight · the state

0.0032EPSSNOT IN KEVas of 2026-09-20
Severity4.3 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defenseunaffected versions publishedreceipt
Movementrisenreceipt
PLATEAU10Minimal movement since 2025-04-01, 514 days at 0.00, as of 2026-08-28. 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 jumpserver? 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

Set up a watchlist (needs a Practitioner account)

Record your call

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

AcceptDeferPatch by…Not affectedMitigated

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.

Reachnetwork-reachable · low privileges required · no user interaction · low attack complexityreceipt
ImpactPartial confidentiality lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-266 Incorrect Privilege Assignmentreceipt
Published consequencesCWE-266: Access Control: Gain Privileges or Assume Identity[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

First unaffected version, by branchjumpserver 3.10.18; jumpserver 4.8.0receipt
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.

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

CVSS, the CNA4.3 MEDIUMreceipt
Exploit probability0.0032 · top 75% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byGitHub_Mreceipt
Recorded changes24 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productjumpserverreceipt
Published rangesfit2cloud jumpserver < 3.10.18; fit2cloud jumpserver >= 4.0.0 < 4.8.0receipt

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

JumpServer is an open source bastion host and an operation and maintenance security audit system. Prior to 4.8.0 and 3.10.18, an attacker with a low-privileged account can access the Kubernetes session feature and manipulate the kubeconfig file to redirect API requests to an external server controlled by the attacker. This allows the attacker to intercept and capture the Kubernetes cluster token. This can potentially allow unauthorized access to the cluster and compromise its security. This vulnerability is fixed in 4.8.0 and 3.10.18. receipt

NVD's analysis a second authority

weakness
CWE-266
affected versions
fit2cloud jumpserver < 3.10.18; fit2cloud jumpserver >= 4.0.0 < 4.8.0
also scored by
[email protected] 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

check it yourself github.com receipt

Movement the material steps

1 Apr 20250.0003
15 Jun 20260.00261 · scoring model v2026.06.15
28 Aug 20260.0032
Show all 24 observations
1 Apr 20250.0003
6 Apr 20250.00033
2 May 20250.00039
7 Jun 20250.00045
31 Jul 20250.00055
27 Aug 20250.00035
28 Aug 20250.00034
8 Sep 20250.0004
25 Oct 20250.00043
4 Nov 20250.00041
13 Nov 20250.00047
18 Nov 20250.00067
21 Nov 20250.00047
4 Dec 20250.00051
15 Dec 20250.00072
25 Dec 20250.00074
15 Jan 20260.0008
25 Jan 20260.00226
9 May 20260.0025
11 May 20260.00421
15 Jun 20260.00261
21 Jun 20260.00285
2 Jul 20260.00307
28 Aug 20260.0032

24 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.0032Published2025-03-31Index as of2026-08-28

The record had been public for 1 year, 4 months when this index was last written.

Published 2025-03-31 receipt · Index as of 2026-08-28 derived

Siblings and hubs

Records related to this one

Browse the index from here

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

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.