The Python developer guide lists 3.10 as end-of-life since October 1, 2026, and the Node.js project marks v20 EOL. Custom software, automation scripts and container images still on either runtime no longer receive upstream fixes.
\nThe Python developer guide lists Python 3.10 as end-of-life with an end date of October 1, 2026, and 3.9 as end-of-life since October 31, 2025. Python 3.11, 3.12 and 3.13 are in the security phase, with scheduled end-of-life months of October 2027, 2028 and 2029. The guide explains that support ends five years after a release, when the release cycle is frozen and no further changes are allowed.
\nThe Node.js releases page marks Node.js 20 and 18 as EOL and v22 and v24 as LTS. It says production applications should only use Active LTS or Maintenance LTS releases, and that starting with Node.js 27 the release cycle becomes annual, with every major version moving to LTS after its Current phase.
\nUse this wherever code runs outside a vendor-managed platform: servers, workstations running automation, serverless functions, CI/CD runners and Docker images. Where a runtime was installed from an operating-system package, check that distribution’s own support statement before deciding whether it still receives fixes.
\nDSE recommends replacing Python 3.10 and Node.js 20 with supported branches in every production workload and build image, starting with internet-facing services. Search repositories for version pins in requirements, runtime and package files, Dockerfiles and pipeline definitions; record each hit with an owner; upgrade dependencies that block the move; and set a recurring review against both projects’ published schedules.
\nAfter each upgrade, run the application’s automated tests and a smoke test in staging, then confirm the deployed process reports the new runtime version. Rebuild container images from updated base images rather than patching running containers, and re-scan the repositories to show that no Python 3.10 or Node.js 20 pins remain.
\nPython Developer’s Guide — Status of Python versions. Node.js — Node.js Releases. Reviewed October 18, 2026.
", "content_text": "The Python developer guide lists 3.10 as end-of-life since October 1, 2026, and the Node.js project marks v20 EOL. Custom software, automation scripts and container images still on either runtime no longer receive upstream fixes.\nSource facts\nThe Python developer guide lists Python 3.10 as end-of-life with an end date of October 1, 2026, and 3.9 as end-of-life since October 31, 2025. Python 3.11, 3.12 and 3.13 are in the security phase, with scheduled end-of-life months of October 2027, 2028 and 2029. The guide explains that support ends five years after a release, when the release cycle is frozen and no further changes are allowed.\nThe Node.js releases page marks Node.js 20 and 18 as EOL and v22 and v24 as LTS. It says production applications should only use Active LTS or Maintenance LTS releases, and that starting with Node.js 27 the release cycle becomes annual, with every major version moving to LTS after its Current phase.\nApplicability\nUse this wherever code runs outside a vendor-managed platform: servers, workstations running automation, serverless functions, CI/CD runners and Docker images. Where a runtime was installed from an operating-system package, check that distribution’s own support statement before deciding whether it still receives fixes.\nDSE recommendation\nDSE recommends replacing Python 3.10 and Node.js 20 with supported branches in every production workload and build image, starting with internet-facing services. Search repositories for version pins in requirements, runtime and package files, Dockerfiles and pipeline definitions; record each hit with an owner; upgrade dependencies that block the move; and set a recurring review against both projects’ published schedules.\nVerification\nAfter each upgrade, run the application’s automated tests and a smoke test in staging, then confirm the deployed process reports the new runtime version. Rebuild container images from updated base images rather than patching running containers, and re-scan the repositories to show that no Python 3.10 or Node.js 20 pins remain.\nOfficial references\nPython Developer’s Guide — Status of Python versions. Node.js — Node.js Releases. Reviewed October 18, 2026.", "content_markdown": "The Python developer guide lists 3.10 as end-of-life since October 1, 2026, and the Node.js project marks v20 EOL. Custom software, automation scripts and container images still on either runtime no longer receive upstream fixes.\n\n## Source facts\n\nThe [Python developer guide](https://devguide.python.org/versions/) lists Python 3.10 as end-of-life with an end date of October 1, 2026, and 3.9 as end-of-life since October 31, 2025. Python 3.11, 3.12 and 3.13 are in the security phase, with scheduled end-of-life months of October 2027, 2028 and 2029. The guide explains that support ends five years after a release, when the release cycle is frozen and no further changes are allowed.\n\nThe [Node.js releases page](https://nodejs.org/en/about/previous-releases) marks Node.js 20 and 18 as EOL and v22 and v24 as LTS. It says production applications should only use Active LTS or Maintenance LTS releases, and that starting with Node.js 27 the release cycle becomes annual, with every major version moving to LTS after its Current phase.\n\n## Applicability\n\nUse this wherever code runs outside a vendor-managed platform: servers, workstations running automation, serverless functions, CI/CD runners and Docker images. Where a runtime was installed from an operating-system package, check that distribution’s own support statement before deciding whether it still receives fixes.\n\n## DSE recommendation\n\nDSE recommends replacing Python 3.10 and Node.js 20 with supported branches in every production workload and build image, starting with internet-facing services. Search repositories for version pins in requirements, runtime and package files, Dockerfiles and pipeline definitions; record each hit with an owner; upgrade dependencies that block the move; and set a recurring review against both projects’ published schedules.\n\n## Verification\n\nAfter each upgrade, run the application’s automated tests and a smoke test in staging, then confirm the deployed process reports the new runtime version. Rebuild container images from updated base images rather than patching running containers, and re-scan the repositories to show that no Python 3.10 or Node.js 20 pins remain.\n\n## Official references\n\n[Python Developer’s Guide — Status of Python versions](https://devguide.python.org/versions/). [Node.js — Node.js Releases](https://nodejs.org/en/about/previous-releases). Reviewed October 18, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/", "url": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-18" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Python 3.10 and Node.js 20 are end-of-life: find them in custom apps, scripts and build images", "item": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/#article", "identifier": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/", "url": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/", "headline": "Python 3.10 and Node.js 20 are end-of-life: find them in custom apps, scripts and build images", "description": "The Python developer guide lists 3.10 as end-of-life since October 1, 2026, and the Node.js project marks v20 EOL. Custom software, automation scripts…", "abstract": "The Python developer guide lists 3.10 as end-of-life since October 1, 2026, and the Node.js project marks v20 EOL. Custom software, automation scripts and container images still on either runtime no longer receive upstream fixes.", "articleBody": "The Python developer guide lists 3.10 as end-of-life since October 1, 2026, and the Node.js project marks v20 EOL. Custom software, automation scripts and container images still on either runtime no longer receive upstream fixes.\nSource facts\nThe Python developer guide lists Python 3.10 as end-of-life with an end date of October 1, 2026, and 3.9 as end-of-life since October 31, 2025. Python 3.11, 3.12 and 3.13 are in the security phase, with scheduled end-of-life months of October 2027, 2028 and 2029. The guide explains that support ends five years after a release, when the release cycle is frozen and no further changes are allowed.\nThe Node.js releases page marks Node.js 20 and 18 as EOL and v22 and v24 as LTS. It says production applications should only use Active LTS or Maintenance LTS releases, and that starting with Node.js 27 the release cycle becomes annual, with every major version moving to LTS after its Current phase.\nApplicability\nUse this wherever code runs outside a vendor-managed platform: servers, workstations running automation, serverless functions, CI/CD runners and Docker images. Where a runtime was installed from an operating-system package, check that distribution’s own support statement before deciding whether it still receives fixes.\nDSE recommendation\nDSE recommends replacing Python 3.10 and Node.js 20 with supported branches in every production workload and build image, starting with internet-facing services. Search repositories for version pins in requirements, runtime and package files, Dockerfiles and pipeline definitions; record each hit with an owner; upgrade dependencies that block the move; and set a recurring review against both projects’ published schedules.\nVerification\nAfter each upgrade, run the application’s automated tests and a smoke test in staging, then confirm the deployed process reports the new runtime version. Rebuild container images from updated base images rather than patching running containers, and re-scan the repositories to show that no Python 3.10 or Node.js 20 pins remain.\nOfficial references\nPython Developer’s Guide — Status of Python versions. Node.js — Node.js Releases. Reviewed October 18, 2026.", "datePublished": "2026-10-18T21:00:04+00:00", "dateModified": "2026-10-18T22:22:06+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/python-3-10-and-node-js-20-end-of-life-runtime-inventory/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Python 3.10 and Node.js 20 are end-of-life: find them in custom apps, scripts and build images" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Checklist", "Advisory priority" ], "genre": "Checklist", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 317, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Python Developer’s Guide — Status of Python versions", "url": "https://devguide.python.org/versions/" } } ] } }