Fix asset graph view leaking DAGs outside the user's permissions#65273
Merged
Conversation
The data-dependency graph endpoint always returned the requested asset node, even when the user had no lineage connection to it through any readable DAG. A user with read access to a single DAG could browse /assets/<id> for any asset in the system and learn its name and any topology fragments reachable through their readable DAGs. The asset is now hidden entirely (404) unless the user has read access to at least one DAG that produces, consumes, or is scheduled by it.
potiuk
requested review from
bugraoz93,
choo121600,
ephraimbuddy,
jason810496,
pierrejeambrun,
rawwar and
shubhamraj-git
as code owners
potiuk
added
the
backport-to-v3-2-test
vatsrahul1001
approved these changes
Apr 15, 2026
Contributor
|
LGTM!, |
Lee-W
approved these changes
Apr 15, 2026
Contributor
Backport successfully created: v3-2-testNote: As of Merging PRs targeted for Airflow 3.X In matter of doubt please ask in #release-management Slack channel.
|
github-actions Bot
pushed a commit
to aws-mwaa/upstream-to-airflow
that referenced
this pull request
Apr 15, 2026
…issions (apache#65273) (cherry picked from commit cf3452d) Co-authored-by: Jarek Potiuk <jarek@potiuk.com>
karenbraganz
pushed a commit
to karenbraganz/airflow
that referenced
this pull request
Apr 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The data-dependency graph endpoint (
/ui/dependencies?node_id=asset:<id>&dependency_type=data)always returned the requested asset node, even when the user had no lineage connection
to it through any readable DAG. A user with read access to even a single DAG could
browse the asset graph page for any asset in the system and learn its name and any
topology fragments reachable through their readable DAGs.
The asset is now hidden entirely (HTTP 404) unless the user has read access to at
least one DAG that produces, consumes, or is scheduled by it. Tasks from non-readable
DAGs continue to be filtered out from the returned graph.
Was generative AI tooling used to co-author this PR?
Generated-by: [Claude Code - Opus 4.6] following the guidelines