Cloudflare Tunnel: docs imply top-level originRequest.access applies to all ingress rules, but cloudflared silently ignores it

Abierto
  • ¿Algo no está bien?
#32,006 1 comentario 0 reacciones 2 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@nikitacano ya está trabajando en esto.

Desde el 10/7/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

product:cloudflare-one stale

Which pages are affected?

What is wrong?

The "Origin configuration" section teaches that a top-level originRequest block sets defaults for all ingress rules, and the access parameter page says to "add the following rule to originRequest" without qualifying where. Following the two pages together, a reasonable reading is that this protects every service behind the tunnel:

originRequest:
  access:
    required: true
    teamName: <team>
    audTag:
      - <aud>

ingress:
  - hostname: app.example.com
    service: http://localhost:8000
  - service: http_status:404

In reality cloudflared silently ignores a top-level access block. The config validates, no warning is logged, and unauthenticated traffic is forwarded to the origin. The JWT validation middleware is only attached when the access block sits under an individual ingress rule: validateIngress in ingress/ingress.go reads the raw per-rule r.OriginRequest.Access, not the merged defaults (the merge in ingress/config.go copies the top-level block, but its result is never consulted for middleware attachment).

Verified on cloudflared 2026.7.1 with an A/B test against the same hostname (no Access app on the hostname, so no JWT on any request): top-level block returned 200 from the origin; the identical block moved under the ingress rule returned 403 from cloudflared.

This is a known cloudflared behaviour: cloudflare/cloudflared#784 (open since 2022) reports it, and a maintainer described it as "largely intended" because Access rules are tied to hostnames. The docs have not been updated to match, which matters because the failure mode is a security control that users believe is active but is not (see also the last comment on that issue).

Suggested fix

  1. In the configuration-file partial's "Origin configuration" section, note that access is an exception to top-level inheritance and must be set on each ingress rule.
  2. In the origin-parameters partial's access section, state explicitly that the block must be placed under originRequest of each individual ingress rule, and that a top-level block is not enforced.
Lenguaje dominante
MDX
Estrellas
5.4k
Forks
17.3k
Merge medio
1 d 19 h
PR fusionados (30 d)
528

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de cloudflare/cloudflare-docs

Todos los issues de cloudflare/cloudflare-docs

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.