CVE-2026-22584
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 · uneditedImproper Control of Generation of Code ('Code Injection') vulnerability in Salesforce Uni2TS on MacOS, Windows, Linux allows Leverage Executable Code in Non-Executable Files.This issue affects Uni2TS: through 1.2.0.
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 confidenceCode injection vulnerability in Salesforce Uni2TS allows execution of code through non-executable files, likely due to unsafe deserialization or improper input validation when processing files on MacOS, Windows, and Linux platforms.
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< 2.0.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.
-
Check installed Uni2TS versionRun the Uni2TS version command (e.g., uni2ts --version, python -c 'import uni2ts; print(uni2ts.__version__)', or check package metadata)Affected if Version is below 2.0.0 (any 1.x.x release)
-
Verify file processing functionality is in useInspect whether Uni2TS is configured to process input files, datasets, or model artifacts from untrusted sourcesAffected if The tool processes files from locations outside your controlled environment
-
Check for deserialization of untrusted dataReview logs or configuration for evidence that Uni2TS deserializes pickled, YAML, JSON, or other serialized objects from input filesAffected if Deserialization of files from untrusted sources is occurring
-
Assess execution environmentConfirm the operating system in use (MacOS, Windows, or Linux) and whether Uni2TS has write access to filesystem locationsAffected if Running on any of the affected platforms with write access to filesystem
You are affected if Uni2TS version is below 2.0.0 and processes files from untrusted or external sources, as this enables the code injection through unsafe deserialization.
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 · scoped2.0.0
Upgrade Uni2TS beyond version 1.2.0 to a patched version; until then, restrict processing to trusted input files and limit access to the tool.
Uni2TS version 2.0.0 or later
- 1. Identify the current installed version of Uni2TS by running: pip show uni2ts or pip list | grep uni2ts
- 2. If the current version is below 2.0.0 (e.g., 1.2.0 or earlier), upgrade to version 2.0.0 or later using: pip install --upgrade uni2ts
- 3. Verify the upgrade was successful by running: pip show uni2ts and confirming the version number is 2.0.0 or higher
- 4. Test that your integration with Uni2TS functions correctly after the upgrade
- 5. If using a requirements.txt or dependency lock file, update the version specification to uni2ts>=2.0.0
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,496.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22584 — 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-22584 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