CVE-2022-41966
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.
XStream Denial of Service via stack overflow
rank 37 = 16 + 19 + 0 + 2 + 0
rank@v1 · scheduled
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.08759 · without this subject the record ranks 21
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 7.5, from NVD · without this subject the record ranks 18
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 37
How much of the world it touches
NVD CPE configurations
1 product in the CPE ranges · without this subject the record ranks 35
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 37
$314,000 = $4.99M incident cost x 0.7179585840212677 exposure x 0.08759 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
Foresight · where to check next
XStream is one instance of CWE-120, buffer copy without checking size of input ('classic buffer overflow'). The index holds 4490 prior instances of this class, 24 KEV-listed. 3 neighbors share the mechanism; each carries its own record state. taxonomy@v1
Sources disagree here.
Both shown, dated. We don't pick winners. disagreement-rules@v1
Running x-stream xstream? 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.
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 affectedMitigatedChoose 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.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Exploit Status & Known PoCs a ladder, not a score
Current rung: Proof-of-concept published · 1 public repository, 2023-01-06.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published · 1 public repository2023-01-06receipt
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
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.
Attack path
What it is stated by the CNA
XStream serializes Java objects to XML and back again. Versions prior to 1.4.20 may allow a remote attacker to terminate the application with a stack overflow error, resulting in a denial of service only via manipulation the processed input stream. The attack uses the hash code implementation for collections and maps to force recursive hash calculation causing a stack overflow. This issue is patched in version 1.4.20 which handles the stack overflow and raises an InputManipulationException instead. receipt
Read the rest of the CNA's description
A potential workaround for users who only use HashMap or HashSet and whose XML refers these only as default map or set, is to change the default implementation of java.util.Map and java.util per the code example in the referenced advisory. However, this implies that your application does not care about the implementation of the map and all elements are comparable.
NVD's analysis a second authority
- severity
- 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- weakness
- CWE-120; CWE-121; CWE-502; CWE-674
- affected versions
- xstream < 1.4.20
- also scored by
- [email protected] 8.2 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
The CNA scored it 8.2 and NVD 7.5. Both are shown because both were published; we do not pick one.
check it yourself github.com x-stream.github.io receipt
Dated events
Movement the material steps
This score more than doubled inside 72 hours. Both observations are in the full history below.
Show all 34 observations
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 pattern, elsewhere
XStream is one instance of CWE-120, buffer copy without checking size of input ('classic buffer overflow'). The index holds 4490 prior instances of this class, 24 KEV-listed. 3 neighbors share the mechanism; each carries its own record state. [email protected]
4490 records in this class held. The six above are ranked by exploit maturity, then recency.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2022-41966.
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.