Skip to content

Remove 'enable_xcom_deserialize_support' because its not used anywhere #51639

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
Jun 13, 2025
Merged
Show file tree
Hide file tree
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 0 additions & 11 deletions RELEASE_NOTES.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3136,17 +3136,6 @@ https://airflow.apache.org/docs/apache-airflow/stable/security/security_model.ht
It is strongly advised to **not** enable the feature until you make sure that only
highly trusted UI/API users have "edit connection" permissions.

The ``xcomEntries`` API disables support for the ``deserialize`` flag by default (#32176)
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
For security reasons, the ``/dags/*/dagRuns/*/taskInstances/*/xcomEntries/*``
API endpoint now disables the ``deserialize`` option to deserialize arbitrary
XCom values in the webserver. For backward compatibility, server admins may set
the ``[api] enable_xcom_deserialize_support`` config to *True* to enable the
flag and restore backward compatibility.

However, it is strongly advised to **not** enable the feature, and perform
deserialization at the client side instead.

Change of the default Celery application name (#32526)
""""""""""""""""""""""""""""""""""""""""""""""""""""""
Default name of the Celery application changed from ``airflow.executors.celery_executor`` to ``airflow.providers.celery.executors.celery_executor``.
Expand Down
17 changes: 17 additions & 0 deletions airflow-core/newsfragments/51639.significant.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
``enable_xcom_deserialize_support`` configuration option has been removed.

This configuration was previously marked as a security risk due to potential remote code execution vulnerabilities
when deserializing arbitrary Python objects that came in from XComs. The removal is a security improvement since
all custom XCom serialization/deserialization is now handled safely at the worker level, making this configuration
unnecessary in core. Users should migrate to not setting this configuration.

* Types of change

* [ ] Dag changes
* [x] Config changes
* [ ] API changes
* [ ] CLI changes
* [ ] Behaviour changes
* [ ] Plugin changes
* [ ] Dependency changes
* [ ] Code interface changes
9 changes: 0 additions & 9 deletions airflow-core/src/airflow/config_templates/config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -1430,15 +1430,6 @@ api:
version_added: 2.2.0
example: ~
default: ""
enable_xcom_deserialize_support:
description: |
Indicates whether the **xcomEntries** endpoint supports the **deserialize**
flag. If set to ``False``, setting this flag in a request would result in a
400 Bad Request error.
type: boolean
version_added: 2.7.0
example: ~
default: "False"
grid_view_sorting_order:
description: |
Sorting order in grid view. Valid values are: ``topological``, ``hierarchical_alphabetical``
Expand Down
4 changes: 2 additions & 2 deletions reproducible_build.yaml
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
release-notes-hash: edb6987ad849473a219f71b63e369800
source-date-epoch: 1749569237
release-notes-hash: 6d40bd86a01a8a2f5ba0d64afc1fb850
source-date-epoch: 1749699565