Origin Validation Error Affecting fort-validator package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.16% (6th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-FORTVALIDATOR-19222745
  • published23 Aug 2026
  • disclosed21 Aug 2026

Introduced: 21 Aug 2026

NewCVE-2026-53499  (opens in a new tab)
CWE-346  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest fort-validator.

NVD Description

Note: Versions mentioned in the description apply only to the upstream fort-validator package and not the fort-validator package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

FORT Validator is a Resource Public Key Infrastructure (RPKI) relying-party validator that produces validated route-origin data. FORT Validator versions through 1.6.7 contain an origin-validation error in their RRDP processing: a delegated CA under the same Trust Anchor Locator (TAL) can reference a victim CA’s public RRDP notification and snapshot URLs, causing FORT’s URL-based download cache to report success after deleting the victim’s local snapshot. Following a routine victim publication, this can silently remove the victim’s VRPs and other signed objects from FORT’s output, potentially enabling route hijacking or loss of reachability. Version 1.6.8 contains a patch that rejects cross-origin RRDP snapshot and delta URLs; as a workaround, administrators can disable HTTP/RRDP with  --http.enabled=false  while keeping rsync enabled, although this can leave data unavailable or stale where rsync is not supported.