Apache Airflow's Backfill API authorized a request against a Dag id supplied by the caller whenever the "backfill_id" path segment failed to parse. The authorization dependency parsed it with "int()" while the route handler parsed it as pydantic's "NonNegativeInt", which accepts values "int()" rejects ("1.0" coerces to "1"); FastAPI resolves dependencies before endpoint validation, so the two acted on different Dags. An authenticated user holding edit permission on any single Dag could therefore read, pause and cancel backfills belonging to any other Dag, including moving another Dag's queued runs to "failed". No non-default configuration is required and backfill ids are sequential, so finding a target is trivial. Users are advised to upgrade to apache-airflow 3.3.1 or later, which parses the backfill id with the same type the routes declare.