rustsec-2026-0263
Vulnerability from osv_rustsec
Published
2026-08-20 12:00
Modified
2026-08-20 15:52
Summary
`tinymember` was removed from crates.io due to affiliation with malicious code
Details
While tinymember did not directly contain malicious code, it was owned by the
same user as arone and aronenao, which contained suspicious build scripts.
This crate had 2 versions published on 2026-08-18 that had a total of 27 downloads. There were no crates depending on this crate on crates.io. The crate was removed from crates.io and the user account was locked.
References
{
"affected": [
{
"database_specific": {
"categories": [],
"cvss": null,
"informational": null
},
"ecosystem_specific": {
"affected_functions": null,
"affects": {
"arch": [],
"functions": [],
"os": []
}
},
"package": {
"ecosystem": "crates.io",
"name": "tinymember",
"purl": "pkg:cargo/tinymember"
},
"ranges": [
{
"events": [
{
"introduced": "0.0.0-0"
}
],
"type": "SEMVER"
}
],
"versions": []
}
],
"aliases": [],
"database_specific": {
"license": "CC0-1.0"
},
"details": "While `tinymember` did not directly contain malicious code, it was owned by the\nsame user as `arone` and `aronenao`, which contained suspicious build scripts.\n\nThis crate had 2 versions published on 2026-08-18 that had a total of 27 downloads.\nThere were no crates depending on this crate on crates.io. The crate was removed\nfrom crates.io and the user account was locked.",
"id": "RUSTSEC-2026-0263",
"modified": "2026-08-20T15:52:09Z",
"published": "2026-08-20T12:00:00Z",
"references": [
{
"type": "PACKAGE",
"url": "https://crates.io/crates/tinymember"
},
{
"type": "ADVISORY",
"url": "https://rustsec.org/advisories/RUSTSEC-2026-0263.html"
},
{
"type": "WEB",
"url": "https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref"
}
],
"related": [],
"severity": [],
"summary": "`tinymember` was removed from crates.io due to affiliation with malicious code"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Loading…
Loading…