vciy

CVE-2023-28126

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.

An authentication bypass vulnerability exists in Avalanche versions 6.3.x and below that could allow an attacker to gain access by exploiting the…

CVE-2023-281264 of 4 sources documented this
34

rank 34 = 17 + 15 + 0 + 2 + 0

rank@v1 · scheduled

Someone is already using it

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

EPSS 0.66659  ·  without this subject the record ranks 17

What it costs you if it fires

NVD CVSS base score, then the CNA's own

CVSS 5.9, from NVD  ·  without this subject the record ranks 19

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 34

How much of the world it touches

NVD CPE configurations

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

Someone else already set the date

CISA KEV remediation due date

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

Unaudited dollar value2 of 3 inputs carry a receipt
Exposure$2.04Mover the next 30 days, if this record is yours
Movement-$419,000on 2025-11-21, the last material move, 6 months before this reading
Basisassumeda published average, not your estate

$2.04M = $4.99M incident cost x 0.6121449559255632 exposure x 0.66659 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.66659EPSSNOT IN KEVas of 2026-09-20
Severity5.9 MEDIUMreceipt
Harmunauthenticated · networkreceipt
Exploitationnone in held sources
Defenseno fix version held
Movementthreshold crossedreceipt
RISING10Risen from 0.00066 to 0.66659 across 34 observations. arc-rules@v1

Foresight · where to check next

CrushFTPVMware ESXiPaperCut MF/NG28126

This record is one instance of CWE-305, authentication bypass by primary weakness. The index holds 172 prior instances of this class, 3 KEV-listed. The nearest of its KEV-listed records are drawn beside this. taxonomy@v1

Full pattern panel

Prior records in this weakness class. Each is its own record, dated and receipted.
Color is a claim, not decoration:the hostile worldthe defenseno signalspoke length is how much of the record matches, not how bad it is

Running Avalanche? 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 · no privileges required · no user interaction · high attack complexityreceipt
ImpactComplete confidentiality lossreceipt
Scored fromCVSS v3.1 · NVD's vectorreceipt
Weakness classCWE-305 Authentication Bypass by Primary Weaknessreceipt
Published consequencesCWE-305: Access Control: Bypass Protection Mechanism[email protected]

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 15 Jun 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.

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, NVD5.9 MEDIUMreceipt
Exploit probability0.66659 · top 0.75% of all CVEsreceipt
Blast breadth1 product across 1 vendorderived
Assigned byhackeronereceipt
Recorded changes34 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productAvalanchereceipt
Published rangesivanti avalanche <= 6.3.4.153receipt

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

An authentication bypass vulnerability exists in Avalanche versions 6.3.x and below that could allow an attacker to gain access by exploiting the SetUser method or can exploit the Race Condition in the authentication message. receipt

NVD's analysis a second authority

severity
5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
weakness
CWE-305; CWE-362
affected versions
ivanti avalanche <= 6.3.4.153
also scored by
5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

check it yourself forums.ivanti.com receipt

Dated events

2025-03-17EPSS moved 0.03 to 0.252026-06-15EPSS moved 0.05 to 0.67

Movement the material steps

10 May 20230.00066
17 Mar 20250.246 · crossed 0.10 · scoring model v2025.03.14
15 Apr 20250.03211 · crossed 0.10
18 Nov 20250.15476 · crossed 0.10
21 Nov 20250.01773 · crossed 0.10
15 Jun 20260.66659 · crossed 0.10 and 0.50 · scoring model v2026.06.15
Show all 34 observations
10 May 20230.00066
17 May 20230.00322
8 Jul 20230.00495
16 Aug 20230.00503
12 Oct 20230.00591
14 Nov 20230.00432
16 Dec 20230.00369
19 Jan 20240.00506
21 Feb 20240.01319
28 Mar 20240.01153
8 Apr 20240.01627
4 May 20240.01232
15 May 20240.01783
10 Jun 20240.02506
19 Oct 20240.02830
29 Nov 20240.02805
17 Dec 20240.03332
25 Feb 20250.02920
11 Mar 20250.02638
17 Mar 20250.246
29 Mar 20250.19818
30 Mar 20250.246
15 Apr 20250.03211
12 May 20250.01773
18 Nov 20250.15476
21 Nov 20250.01773
30 Nov 20250.00852
18 Dec 20250.00616
1 Jan 20260.00463
1 Feb 20260.00394
5 Mar 20260.00337
11 May 20260.01876
9 Jun 20260.04671
15 Jun 20260.66659

34 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.66659Published2023-05-09Index as of2026-06-15

The record had been public for 3 years, 1 month when this index was last written.

Published 2023-05-09 receipt · Index as of 2026-06-15 derived

The pattern, elsewhere

This record is one instance of CWE-305, authentication bypass by primary weakness. The index holds 172 prior instances of this class, 3 KEV-listed. The nearest of its KEV-listed records are drawn beside this. [email protected]

CVE-2025-31161 · CrushFTPmatches 5 of 10KEV listed · 2025receipt
CVE-2024-37085 · VMware ESXimatches 3 of 10KEV listed · 2024receipt
CVE-2026-81578 · PaperCut MF/NGonly 2 attributes comparableKEV listed · 2026receipt

"Matches n of m" counts the attributes the two records can both be compared on: the CVSS metrics they share a version of, any weakness class beyond this one, and the vendor. fit-rules@v1

172 records in this class held. The six above are drawn from the ones CISA has listed as exploited, ranked by how much of the record matches this one. That is why every one of them is KEV-listed: the pool is, so the colour on those spokes says nothing the pool has not already said.

No curated product neighbourhood is held for this product, so the records above are the nearest this index can name. The neighbourhood table covers a small set of products and is extended by hand.

Siblings and hubs

Records related to this one

Browse the index from here

These are index-wide views, not findings about CVE-2023-28126.

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.