It depends on what your Airflow deployment looks like. Is your Airflow deployed on Kubernetes? Then the file system gets set on fire after each task completes. Pods are ephemeral or short lived. So there's nothing to access in the later task.

If you're running everything on a single EC2, then yes it might be feasible. But it's an antipattern in my opinion and according to Airflow's docs. The cross-task communication mechanism in Airflow is Xcoms.

Airflow's example xcoms DAG should be helpful for getting started with the feature.