CVE-2025-57622
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 · uneditedAn issue in Step-Video-T2V allows a remote attacker to execute arbitrary code via the /vae-api , /caption-api , feature = pickle.loads(request.get_data()) component
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 confidenceStep-Video-T2V contains a critical insecure deserialization vulnerability where the /vae-api and /caption-api endpoints directly pass user-controlled request data to pickle.loads(). This allows remote attackers to execute arbitrary code by sending crafted malicious pickle payloads, achieving unauthenticated RCE with network access.
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
- 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 Step-Video-T2V installationLocate the application directory or running process for Step-Video-T2V. Check for files like vae_api.py, caption_api.py, or main application entry points. Use 'ps aux | grep -i step' or inspect running container/process listings.Affected if Step-Video-T2V software is present in the environment
-
Verify vulnerable API endpoints are exposedReview your web server or API gateway configuration, routing rules, or application code to confirm whether /vae-api and /caption-api endpoints are publicly or internally accessible. Check for route definitions like '@app.route("/vae-api")' or '@app.route("/caption-api")'.Affected if Either /vae-api or /caption-api endpoints are enabled and reachable
-
Confirm pickle deserialization with user inputInspect the source code for the /vae-api and /caption-api endpoints. Search for patterns like 'pickle.loads(request.' or 'pickle.loads(data' where request/data originates from user input without sanitization. Review the endpoint handler functions directly.Affected if Code passes raw user-controlled data directly to pickle.loads() without validation or safe deserialization
-
Check API authentication statusExamine the endpoint handlers and surrounding middleware for authentication/authorization decorators or checks (e.g., @login_required, @require_auth, session validation). Determine if these endpoints allow unauthenticated access.Affected if The vulnerable endpoints are accessible without authentication
-
Assess network exposureReview firewall rules, reverse proxy configuration, or API gateway settings to determine if these endpoints are exposed to untrusted networks. Check if the service binds to 0.0.0.0 versus localhost only.Affected if The API endpoints are reachable from network locations beyond trusted internal clients
The environment is affected if Step-Video-T2V is running with /vae-api or /caption-api endpoints exposed and the code directly deserializes user input via pickle.loads() without authentication or 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 dataReplace pickle.loads() with safe deserialization (e.g., JSON) and validate all incoming API data before processing. If pickle is required, implement cryptographic signing/verification of serialized data.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-57622 — 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-57622 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