RustFS gRPC GetMetrics deserialization panic enables remote DoS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

5.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2025-69255: 0.34% estimated exploitation activity in the next 30 days; percentile 27.16 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary A malformed gRPC GetMetrics request causes getmetrics to unwrap() failed deserialization of metrictype/opts, panicking the handler thread and enabling remote denial of service of the metrics endpoint. Details - Vulnerable code: rustfs/src/storage/tonicservice.rs:1775-1782: - MetricType and CollectMetricsOpts are deserialized with Deserialize::deserialize(...).unwrap() from client-supplied bytes. - Malformed metrictype/opts (e.g., empty or truncated rmp-serde payloads) trigger InvalidMarkerRead and panic. - Reachability: same TCP listener as S3 (default :9000); only a static interceptor token authorization: rustfs rpc is checked in server/http.rs:677. - Impact scope: panic terminates the worker handling the request, causing metrics service interruption and potential process instability. PoC rustfs-grpc-metrics-invalid-metric-type-panic-poc.tar.gz 1) Start RustFS (example local dev): 2) From rustfs-grpc-metrics-invalid-metric-type-panic-poc/, run: 3) Observe panic in server…

Published by the source

7 Jan 2026, 18:36 UTC

Last modified by the source

7 Jan 2026, 21:34 UTC

Source last checked

26 Oct 2026, 15:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gw2x-q739-qhcr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-69255

Advisory: RustFS gRPC GetMetrics deserialization panic enables remote DoS
IDs: CVE-2025-69255, GHSA-gw2x-q739-qhcr
Record: https://patchnext.com/advisories/cve-2025-69255 (revision 1, source checked 26 Oct 2026, 15:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: rustfs 1.0.0-alpha.78. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io rustfs: affected >= 1.0.0-alpha.13, <= 1.0.0-alpha.77; fixed in 1.0.0-alpha.78

## Suggested inspection (read-only)
- crates.io rustfs: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on rustfs.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gw2x-q739-qhcr (GitHub-reviewed advisory GHSA-gw2x-q739-qhcr lists affected ranges: crates.io rustfs >=1.0.0-alpha.13 <=1.0.0-alpha.77)

Commands are suggestions: review each one before running it.