potiuk commented on code in PR #61956: URL: https://github.com/apache/airflow/pull/61956#discussion_r2809741348
########## airflow-core/docs/security/vulnerabilities-in-3rd-party-dependencies.rst: ########## @@ -0,0 +1,132 @@ + .. Licensed to the Apache Software Foundation (ASF) under one + or more contributor license agreements. See the NOTICE file + distributed with this work for additional information + regarding copyright ownership. The ASF licenses this file + to you under the Apache License, Version 2.0 (the + "License"); you may not use this file except in compliance + with the License. You may obtain a copy of the License at + + .. http://www.apache.org/licenses/LICENSE-2.0 + + .. Unless required by applicable law or agreed to in writing, + software distributed under the License is distributed on an + "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY + KIND, either express or implied. See the License for the + specific language governing permissions and limitations + under the License. + +Vulnerabilities in 3rd party dependencies +========================================= + +How users should treat 3rd-party dependencies with known CVEs +------------------------------------------------------------- + +Apache Airflow has rather big number of dependencies, and we invest a lot of effort to keep Airflow updated +to latest versions of those dependencies. We have automation, that checks for new versions of dependencies, +and attempts to upgrade and test them automatically, we also have security scans that indicate if we have +minimum versions of dependencies, that are not vulnerable to known, important, exploitable CVEs. Every +version of Airflow has a set of constraints - i.e. latest tested versions of dependencies, that +are passing our tests and that we know allow to install Airflow an it's providers together. + +However - due to sometimes complex dependency trees and sometimes conflicting requirements, we are not +always able to upgrade and test dependencies to the latest versions. Sometimes we can only upgrade to newer +versions of dependencies in the "development" branch - i.e. for the next "MINOR" version of Airflow, +and we are not able to backport those upgrades to the latest released "MINOR" version of Airflow. + +This means that sometimes we have to keep older versions of dependencies in the latest released "MINOR" +version of Airflow, even if those versions are vulnerable to some CVEs. Since Airflow is volunteer-driven Review Comment: ```suggestion version of Airflow, even if those versions are vulnerable to some CVEs. Since Airflow is a volunteer-driven ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
