dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-10974

MEDIUM · 6.3 CVSS v3.1 Published 2025-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability has been found in giantspatula SewKinect up to 7fd963ceb3385af3706af02b8a128a13399dffb1. This affects the function pickle.loads of the file /calculate of the component Endpoint. Such manipulation of the argument body_parts/point_cloud leads to deserialization. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases.

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 · high confidence

The SewKinect application uses pickle.loads() to deserialize data from the /calculate endpoint without sanitization. The body_parts and point_cloud parameters accept attacker-controlled data that gets passed directly to pickle.loads(), enabling remote code execution through malicious serialized Python objects.

MitigationReplace pickle.loads() with a safe deserialization method (e.g., JSON) and implement input validation on the /calculate endpoint parameters.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SewKinect is deployed
    Search for files or directories named 'sewkinect', 'SewKinect', or check running processes/services containing 'sewkinect' in the name. Review web server configurations for applications handling sewing/kinect data.
    Affected if SewKinect application is present in the environment
  2. Locate the /calculate endpoint code
    Search the application source code for route definitions containing '/calculate'. Common locations include app.py, main.py, views.py, or API route files. Look for decorators like @app.route('/calculate') or equivalent routing definitions.
    Affected if A /calculate endpoint exists and handles requests
  3. Inspect deserialization logic on body_parts and point_cloud parameters
    Examine the code handling the /calculate endpoint. Search for occurrences of 'pickle.loads' and trace whether body_parts or point_cloud request parameters are passed to it. grep for 'pickle.loads' near the calculate endpoint code.
    Affected if pickle.loads() is called with data from body_parts or point_cloud parameters without prior safe deserialization
  4. Verify if input validation exists before pickle.loads
    Review the code flow before pickle.loads() calls. Look for any JSON parsing (json.loads), input validation, or sanitization functions applied to body_parts or point_cloud. Check if the data type is explicitly validated before deserialization.
    Affected if No validation or sanitization occurs before pickle.loads() processes body_parts or point_cloud data
  5. Confirm the endpoint accepts external input
    Check the HTTP method and parameter handling of /calculate. Verify that body_parts and point_cloud are received from request body, query parameters, or headers without authentication requirements or network restrictions.
    Affected if The /calculate endpoint accepts body_parts or point_cloud from unauthenticated or external requests

If SewKinect is deployed, the /calculate endpoint exists, and code inspection shows pickle.loads() receiving body_parts or point_cloud parameters without prior JSON parsing or validation, the environment is affected by CVE-2025-10974.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace pickle.loads() with a safe deserialization method (e.g., JSON) and implement input validation on the /calculate endpoint parameters.

Recommended fix Moderate confidence
  1. 1. Do not use pickle.loads with untrusted or user-supplied input. Replace pickle serialization with safer alternatives like JSON, MessagePack, or protobuf.
  2. 2. If pickle deserialization is absolutely required, implement a custom Unpickler class that restricts what classes can be deserialized using the `find_class` method to whitelist allowed types.
  3. 3. Alternatively, migrate the /calculate endpoint to accept JSON input instead of pickled Python objects for the body_parts/point_cloud parameters.
  4. 4. Implement input validation on the endpoint to verify data types and structure before any deserialization occurs.
  5. 5. If possible, add network-level restrictions to limit who can access the /calculate endpoint.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-10974 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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