vciy

CVE-2025-61984

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.

ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code…

CVE-2025-619843 of 4 sources documented this
24

rank 24 = 15 + 9 + 0 + 0 + 0

rank@v1 · backlog

Someone is already using it

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

EPSS 0.00286  ·  without this subject the record ranks 9

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 3.6, from the CNA  ·  without this subject the record ranks 15

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 24

How much of the world it touches

NVD CPE configurations

0 products in the CPE ranges  ·  without this subject the record ranks 24

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$6,110over 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

$6,110 = $4.99M incident cost x 0.42806422275080447 exposure x 0.00286 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.00286EPSSNOT IN KEVas of 2026-09-20
Severity3.6 LOWreceipt
Harmpartial impactreceipt
Exploitationpublic proof-of-conceptreceipt
Defensefix version namedreceipt
Movementdoubled within 72hreceipt
PLATEAU10Minimal movement since 2025-10-07, 334 days at 0.00, as of 2026-09-06. 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 OpenBSD OpenSSH? 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.

Reachneeds local access · low privileges required · no user interaction · high attack complexityreceipt
ImpactPartial confidentiality and integrity lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-159 Improper Handling of Invalid Use of Special Elementsreceipt
Published consequencesCWE-159: Integrity: Unexpected State[email protected]

CISA KEV & Federal Remediation Deadline from the record and CISA

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

Fixed in10.1receipt
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: Proof-of-concept published · 2 public repositories, 2025-10-07.

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

Authority who says so

CVSS, the CNA3.6 LOWreceipt
Exploit probability0.00286 · top 79% of all CVEsreceipt
Assigned bymitrereceipt
Recorded changes33 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productOpenBSD OpenSSHreceipt
Fixed in10.1receipt

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

ssh in OpenSSH before 10.1 allows control characters in usernames that originate from certain possibly untrusted sources, potentially leading to code execution when a ProxyCommand is used. The untrusted sources are the command line and %-sequence expansion of a configuration file. (A configuration file that provides a complete literal username is not categorized as an untrusted source.) receipt

NVD's analysis a second authority

weakness
CWE-159
also scored by
[email protected] 3.6 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

check it yourself openwall.com marc.info openssh.com receipt

Movement the material steps

7 Oct 20250.00011
15 Jun 20260.00221 · scoring model v2026.06.15
6 Sep 20260.00286

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

Show all 30 observations
7 Oct 20250.00011
12 Oct 20250.00013
7 Nov 20250.00015
15 Nov 20255e-05
18 Nov 20250.00015
19 Nov 20255e-05
21 Nov 20256e-05
1 Dec 20255e-05
4 Dec 20256e-05
13 Dec 20257e-05
1 Jan 20266e-05
4 Jan 20267e-05
1 Feb 20266e-05
4 Feb 20267e-05
5 Feb 20268e-05
1 Mar 20267e-05
4 Mar 20265e-05
16 Mar 20266e-05
21 Mar 20260.00011
2 May 20260.00013
16 May 20260.00014
19 May 20260.00013
27 May 20260.00012
15 Jun 20260.00221
2 Jul 20260.00218
3 Jul 20260.00211
12 Jul 20260.00218
15 Jul 20260.00284
5 Aug 20260.00275
6 Sep 20260.00286

30 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.00286Published2025-10-06Public PoC2025-10-07Index as of2026-09-06

Exploit probability more than doubled between 2025-11-15 and 2025-11-18 (0.00005 → 0.00015) and the record had been public for 11 months when this index was last written.

Published 2025-10-06 receipt · Public PoC 2025-10-07 receipt · Index as of 2026-09-06 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

Listed because one advisory covers them, not because they are the same defect. Each record's own state is on its own page.

Grouping: held values

Browse the index from here

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

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.