Security advisory
A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2024-56169
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 2 Nov 2026, 19:17 UTC · Revision 1
Source evidence
A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.
osv:CVE-2024-56169
Complete source record
{
"id": "89ab4f8409c84ac646b1ebcd05f5f06c2ccae4d12d6bd3c9b1f9c3a81a0616e5",
"url": "https://osv.dev/vulnerability/CVE-2024-56169",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2024-56169",
"summary": "A validation integrity issue was discovered in Fort through 1.6.4 before 2.0.0. RPKI Relying Parties (such as Fort) are supposed to maintain a backup cache of the remote RPKI data. This can be employed as a fallback in case a new fetch fails or yields incorrect files. However, the product currently uses its cache merely as a bandwidth saving tool (because fetching is performed through deltas). If a fetch fails midway or yields incorrect files, there is no viable fallback. This leads to incomplete route origin validation data.",
"evidence": "osv:CVE-2024-56169",
"products": [],
"severity": "medium",
"structured": {
"id": "CVE-2024-56169",
"aliases": [
"CVE-2024-56169"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/nicmx/fort-validator",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"last_affected": "b0914e8cf864dabc99db81d247054e063c71e003"
}
],
"database_specific": {
"extracted_events": [
{
"range": [
{
"introduced": "0"
},
{
"last_affected": "1.6.4"
}
],
"source": "DESCRIPTION"
},
{
"cpe": "cpe:2.3:a:nicmx:fort_validator:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"last_affected": "1.6.6"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"1.6.4",
"1.6.3",
"1.6.2",
"1.6.1",
"1.6.0",
"1.5.4",
"1.5.3",
"v1.5.1",
"v1.5.0",
"v1.4.0",
"v1.3.0",
"v1.2.1",
"v1.2.0",
"v1.1.1",
"v1.1.0",
"v1.0.0",
"v0.0.2"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2024-56169.json"
}
}
],
"modified": "2026-10-28T02:30:22.966803793Z",
"provider": "osv",
"references": [
"https://nicmx.github.io/FORT-validator/CVE.html",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56169.json",
"https://nvd.nist.gov/vuln/detail/CVE-2024-56169",
"https://github.com/NICMx/FORT-validator/issues/82"
],
"provider_metadata": {
"cna_assigner": "mitre",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"fixed": "2.0.0"
}
],
"source": "DESCRIPTION"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2024/56xxx/CVE-2024-56169.json"
}
},
"related_cves": [
{
"value": "CVE-2024-56169",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 489068,
"published_at": "2024-12-18T00:00:00+00:00"
}