CVE-2025-60889
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInsecure deserialization of untrusted input in StellarGroup HPX 1.11.0 under certain conditions may allow attackers to execute arbitrary code or other unspecified impacts.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceHPX 1.11.0 contains an insecure deserialization vulnerability where untrusted input is processed without proper validation, allowing attackers to potentially execute arbitrary code through malicious serialized data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 1.11.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed HPX versionRun 'hpxd --version' or check the package manager for installed hpx package version, or inspect the linked library version in your applicationAffected if The installed version is 1.11.0 or any lower version (e.g., 1.10.x, 1.9.x)
-
Locate HPX serialization usage in codebaseSearch source code for includes of HPX serialization headers such as '<hpx/serialization/serialize.hpp>' or usage of 'hpx::serialization::serialize' functionsAffected if Your code uses HPX serialization facilities to deserialize data
-
Identify deserialization call sitesSearch for calls to 'hpx::serialization::load', 'hpx::serialization::deserialize', or input stream operators ('>>') used with HPX archive types on external dataAffected if Code deserializes data from external or network sources without validation
-
Verify source of deserialized dataAudit data flow: check if deserialized data originates from user input, network sockets, files uploaded by users, or other untrusted sourcesAffected if Deserialized data comes from untrusted or remote sources without sanitization
-
Check for unsafe archive type usageInspect which HPX archive types are used (binary_archive, text_archive, json_archive). Look for polymorphic archives or any_type support without allowlistingAffected if Binary archives from untrusted sources are being deserialized, or type allowlisting is not enforced
You are affected if HPX version is 1.11.0 or lower AND your application deserializes data from untrusted sources using HPX serialization features without input validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version if available; otherwise, implement strict input validation and avoid deserializing data from untrusted sources, or use safer serialization formats such as JSON with allowlisted types.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60889 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-60889 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data