CVE-2026-25360
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 · uneditedDeserialization of Untrusted Data vulnerability in rascals Vex vex allows Object Injection.This issue affects Vex: from n/a through < 1.2.9.
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 confidenceDeserialization of Untrusted Data vulnerability in the Vex library (rascals/Vex) allows Object Injection. This is a code injection vulnerability where untrusted data deserialized by the application can be manipulated to instantiate arbitrary objects, potentially leading to remote code execution. The issue affects all versions prior to 1.2.9.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed Vex library versionLocate the Vex library in your project's dependency manifest (such as package.json for Node.js, Gemfile for Ruby, composer.json for PHP, or requirements.txt for Python) and note the version number specified. If using a package manager, you can also run a version query command (for example, 'npm list vex' or 'pip show vex') to retrieve the installed version.Affected if The version is lower than 1.2.9 or no version is specified (implying an unpatched release).
-
Determine if deserialization is used in your codebaseSearch your application source code for usage of deserialization functions that process data from the Vex library. Look for patterns such as unserialize(), json_decode() when used with untrusted input, YAML parsing of external data, or similar deserialization calls. Review any endpoints or functions that accept serialized data and pass it to the Vex library.Affected if Your application deserializes data from untrusted sources using the Vex library, and the library version is below 1.2.9.
-
Review Vex library usage in your applicationExamine the files where the Vex library is imported or referenced. Check if the library is used to parse, render, or process content that could originate from user input, external APIs, or uploaded files. Look for any code paths where external data flows into Vex library functions.Affected if The Vex library processes untrusted input and the installed version is prior to 1.2.9.
You are affected if your installed Vex library version is below 1.2.9 AND your application uses the library to deserialize or process data from untrusted sources.
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.
dbcve · scopedUpgrade the Vex library to version 1.2.9 or later. Review any deserialization paths in code using this library and ensure external input is validated before deserialization.
Upgrade to Vex version 1.2.9 or later
- Identify the current version of Vex library/package being used in the project
- Upgrade Vex to version 1.2.9 or later by updating the dependency in your project's package manager (e.g., npm, pip, or gem depending on the language)
- Run the upgrade command (e.g., npm update vex, pip install --upgrade vex, or gem update vex)
- Verify the new version is installed by checking the installed package version
- Restart any services or applications using the Vex library
- Test the application functionality to ensure the upgrade does not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25360 — 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-2026-25360 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