vciy

CVE-2024-32765

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.

QTS, QuTS hero

CVE-2024-327654 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.00211  ·  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.2, 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$6,050over 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,050 = $4.99M incident cost x 0.5743756121449558 exposure x 0.00211 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.00211EPSSNOT IN KEVas of 2026-09-20
Severity4.2 MEDIUMreceipt
Harmpartial impactreceipt
Exploitationnone in held sources
Defensefix version namedreceipt
Movementscoring model changedreceipt
PLATEAU10Minimal movement since 2024-08-13, 671 days at 0.00, as of 2026-06-15. 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 QNAP Systems Inc. QTS? 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 · high privileges required · no user interaction · low attack complexityreceipt
ImpactPartial confidentiality, integrity and availability lossreceipt
Scored fromCVSS v3.1 · the CNA's vectorreceipt
Weakness classCWE-291 Reliance on IP Address for Authentication; CWE-306 Missing Authentication for Critical Functionreceipt
Published consequencesCWE-291: Access Control, Non-Repudiation: Hide Activities, 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.

Fixed in5.1.8.2823 build 20240712receipt
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.2 MEDIUMreceipt
Exploit probability0.00211 · top 88% of all CVEsreceipt
Blast breadth2 products across 1 vendorderived
Assigned byqnapreceipt
Recorded changes18 · last 19 Sep 2026derived

Affected & Fixed Versions as published

Affected productQNAP Systems Inc. QTS; QNAP Systems Inc. QuTS heroreceipt
Published rangesqnap qts >= 5.1.0 < 5.1.8.2823; qnap quts hero >= h5.1.0 < h5.1.8.2823receipt
Fixed in5.1.8.2823 build 20240712receipt

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

A vulnerability has been reported to affect Network & Virtual Switch. If exploited, the vulnerability could allow local authenticated administrators to gain access to and execute certain functions via unspecified vectors. We have already fixed the vulnerability in the following versions: QTS 5.1.8.2823 build 20240712 and later QuTS hero h5.1.8.2823 build 20240712 and later receipt

NVD's analysis a second authority

weakness
CWE-291; CWE-306
affected versions
qnap qts >= 5.1.0 < 5.1.8.2823; qnap quts hero >= h5.1.0 < h5.1.8.2823
also scored by
[email protected] 4.2 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L

check it yourself qnap.com receipt

Movement the material steps

13 Aug 20240.00043
17 Mar 20250.0003 · scoring model v2025.03.14
15 Jun 20260.00211 · scoring model v2026.06.15
Show all 18 observations
13 Aug 20240.00043
26 Aug 20240.00065
17 Mar 20250.0003
14 Apr 20250.00033
15 Apr 20250.00024
25 Apr 20250.00025
5 May 20250.00026
5 Jun 20250.00027
17 Sep 20250.00069
18 Sep 20250.00014
20 Sep 20250.00017
21 Sep 20250.00015
23 Sep 20250.00013
18 Nov 20250.00038
21 Nov 20250.00013
11 Dec 20250.00024
29 Dec 20250.00032
15 Jun 20260.00211

18 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.00211Published2024-08-09Index as of2026-06-15

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

Published 2024-08-09 receipt · Index as of 2026-06-15 derived

Siblings and hubs

Records related to this one

Fixed with these, by one advisory

qsa-24-14

Of the 3 records in this advisory, this is the only one holding a stated fix version: 5.1.8.2823 build 20240712.

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-2024-32765.

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.