# RUSTSEC-2025-0117: tandem is unmaintained

> The tandem library is unmaintained and archived, requiring users to migrate to the Polytune alternative to ensure security and support.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 10 Nov 2025

## What is RUSTSEC-2025-0117?

RUSTSEC-2025-0117 is a vulnerability in tandem, published on 10 Nov 2025. 

### Official description

The tandem crates in [https://github.com/sine-fdn](github.com/sine-fdn) are no longer maintained by the SINE Foundation. The repository has been archived.

## Recommended alternative
We are continuing our work on SMPC by implementing our secure multi-party computation engine [Polytune](https://github.com/sine-fdn/polytune).

## Which versions are affected by RUSTSEC-2025-0117?

1 open source package ship an affected version, including tandem.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tandem` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2025-0117?

No fix has been published for RUSTSEC-2025-0117 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2025-0117 being exploited?

There is no known exploitation of RUSTSEC-2025-0117 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2025-0117 and fix it if it is affected.

What it is: RUSTSEC-2025-0117 is a vulnerability in tandem, published on 10 Nov 2025. 
Exploitation: There is no known exploitation of RUSTSEC-2025-0117 in the wild and no public exploit code.

Affected packages and fixed versions:
- tandem (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2025-0117/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0117/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2025-0117

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2025-0117/
Summaries are generated and may contain mistakes; the official description above is the record.