# Fly Replay Attack

**URL:** <https://community.fly.io/t/fly-replay-attack/27400>\
**Category:** General\
**Tags:** security, proxy, login-only\
**Created:** [March 19, 2026, 7:05pm UTC](https://community.fly.io/t/fly-replay-attack/27400 "2026-03-19T19:05:12Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![felixchen1998](https://avatars.discourse-cdn.com/v4/letter/f/e56c9b/32.png) [@felixchen1998](https://community.fly.io/u/felixchen1998)\
**Post date:** [March 19, 2026, 7:05pm UTC](https://community.fly.io/t/fly-replay-attack/27400/1 "2026-03-19T19:05:12Z")

</div>

I need tenant isolation in my application, tenant’s have full control of their machines, and can in theory put secrets on them.

The current setup:

1. Server App
2. Tenant App

- On a custom private network
- has a flycast IP from the server App ([Custom private networks · Fly Docs](https://fly.io/docs/networking/custom-private-networks/#private-apps-with-flycast))

My question is can a tenant machine be written to respond with fly replay to get a request to run on another tenant’s machine ? [Custom private networks · Fly Docs](https://fly.io/docs/networking/custom-private-networks/#forward-requests-with-the-fly-replay-response-header) . Fly Replay seems to proxy to any application within the organization without needing any permissions. ([Dynamic Request Routing with fly-replay · Fly Docs](https://fly.io/docs/networking/dynamic-request-routing/#cross-app-routing))

---

<div class="post-metadata">

**Author:** ![felixchen1998](https://avatars.discourse-cdn.com/v4/letter/f/e56c9b/32.png) [@felixchen1998](https://community.fly.io/u/felixchen1998)\
**Post date:** [March 19, 2026, 8:18pm UTC](https://community.fly.io/t/fly-replay-attack/27400/2 "2026-03-19T20:18:05Z")

</div>

┌────────────────┬──────────────────────────────────────────────┐  
│ Attack │ Result │  
├────────────────┼──────────────────────────────────────────────┤  
│ fly-replay │ BREACH — Fly Proxy replayed the request to │  
│ injection │ pingpong despite our proxy stripping the │  
│ │ header │  
├────────────────┼──────────────────────────────────────────────┤  
│ flycast direct │ PASS — blocked (DNS/routing isolated) │  
│ probe │ │  
├────────────────┼──────────────────────────────────────────────┤  
│ DNS resolution │ PASS — blocked (no cross-network resolution) │  
│ probe │ │  
├────────────────┼──────────────────────────────────────────────┤  
│ .fly.dev │ PASS — blocked │  
│ bypass │ │  
└────────────────┴──────────────────────────────────────────────┘

The critical finding: the fly-replay header from mallory’s response  
caused Fly Proxy to replay the original request directly to  
pingpong, bypassing the cloud-harness proxy entirely. Look at the  
evidence in pingpong’s log:

- fly-replay-src: instance=xyz — that’s mallory’s machine  
ID
- fly-dispatch-start: … instance=abc — dispatched  
directly to pingpong
- The request path is /attack/replay — the original client request  
was replayed to pingpong

---

<div class="post-metadata">

**Author:** ![felixchen1998](https://avatars.discourse-cdn.com/v4/letter/f/e56c9b/32.png) [@felixchen1998](https://community.fly.io/u/felixchen1998)\
**Post date:** [March 19, 2026, 8:18pm UTC](https://community.fly.io/t/fly-replay-attack/27400/3 "2026-03-19T20:18:53Z")

</div>

Fly replay can go across all apps in the org by default. Need org level isolation.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\
**Post date:** [March 26, 2026, 8:31pm UTC](https://community.fly.io/t/fly-replay-attack/27400/5 "2026-03-26T20:31:45Z")

</div>

Closed on March 26, 2026, 8:31pm UTC

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
