nano-id is unable to generate the correct character set
nano-id is a unique string ID generator for Rust. Affected versions of the nano-id crate incorrectly generated IDs using a reduced character set in the `nano_id::base62` and `nano_id::base58` functions. Specifically, the `base62` function used a character set of 32 symbols instead of the intended 62 symbols, and the `base58` function used a character set of 16 symbols instead of the intended 58 symbols. Additionally, the `nano_id::gen` macro is also affected when a custom character set that is not a power of 2 in size is specified. It should be noted that `nano_id::base64` is not affected by this vulnerability. This can result in a significant reduction in entropy, making the generated IDs predictable and vulnerable to brute-force attacks when the IDs are used in security-sensitive contexts such as session tokens or unique identifiers. The vulnerability is fixed in 0.4.0.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-36400
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 07:08 UTC · Revision 1
Source evidence
nano-id is unable to generate the correct character set
core-osv · Original sourcePublished 4 Jun 2024, 14:11 UTC
nano-id is a unique string ID generator for Rust. Affected versions of the nano-id crate incorrectly generated IDs using a reduced character set in the `nano_id::base62` and `nano_id::base58` functions. Specifically, the `base62` function used a character set of 32 symbols instead of the intended 62 symbols, and the `base58` function used a character set of 16 symbols instead of the intended 58 symbols. Additionally, the `nano_id::gen` macro is also affected when a custom character set that is not a power of 2 in size is specified. It should be noted that `nano_id::base64` is not affected by this vulnerability. This can result in a significant reduction in entropy, making the generated IDs predictable and vulnerable to brute-force attacks when the IDs are used in security-sensitive contexts such as session tokens or unique identifiers. The vulnerability is fixed in 0.4.0.
osv:CVE-2024-36400
Complete source record
{
"id": "71b041c9a4931ade8b605482a7facbc07e1c960f5c4284a1d166cbe0d848fd6a",
"url": "https://osv.dev/vulnerability/CVE-2024-36400",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "nano-id is unable to generate the correct character set",
"summary": "nano-id is a unique string ID generator for Rust. Affected versions of the nano-id crate incorrectly generated IDs using a reduced character set in the `nano_id::base62` and `nano_id::base58` functions. Specifically, the `base62` function used a character set of 32 symbols instead of the intended 62 symbols, and the `base58` function used a character set of 16 symbols instead of the intended 58 symbols. Additionally, the `nano_id::gen` macro is also affected when a custom character set that is not a power of 2 in size is specified. It should be noted that `nano_id::base64` is not affected by this vulnerability. This can result in a significant reduction in entropy, making the generated IDs predictable and vulnerable to brute-force attacks when the IDs are used in security-sensitive contexts such as session tokens or unique identifiers. The vulnerability is fixed in 0.4.0.",
"evidence": "osv:CVE-2024-36400",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2024-36400",
"aliases": [
"CVE-2024-36400",
"GHSA-2hfw-w739-p7x5",
"GHSA-9hc7-6w9r-wj94",
"RUSTSEC-2024-0343"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/viz-rs/nano-id",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "2209b317ae4ea4caa982a09b0a8e5c0621dd4f83"
},
{
"fixed": "a9022772b2f1ce38929b5b81eccc670ac9d3ab23"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:viz:nano_id:*:*:*:*:*:rust:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "0.4.0"
}
],
"source": "CPE_RANGE"
},
{
"range": [
{
"fixed": "a9022772b2f1ce38929b5b81eccc670ac9d3ab23"
}
],
"source": "REFERENCES_COMMIT"
}
]
}
}
],
"versions": [
"v0.3.2",
"v0.3.1",
"v0.2.1",
"v0.2.0",
"v0.1.1",
"v0.1.0",
"v0.0.1"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-36400.json"
}
}
],
"modified": "2026-10-28T02:30:26.760789990Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/36xxx/CVE-2024-36400.json",
"https://github.com/viz-rs/nano-id/security/advisories/GHSA-9hc7-6w9r-wj94",
"https://nvd.nist.gov/vuln/detail/CVE-2024-36400",
"https://github.com/viz-rs/nano-id/commit/a9022772b2f1ce38929b5b81eccc670ac9d3ab23"
],
"provider_metadata": {
"cwe_ids": [
"CWE-331"
],
"cna_assigner": "GitHub_M",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/36xxx/CVE-2024-36400.json"
}
},
"related_cves": [
{
"value": "CVE-2024-36400",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 493255,
"published_at": "2024-06-04T14:11:26.945+00:00"
}