SecurityCustomer identity

Auth0 is pulling Node 18 out from under your login code. Here's how to move it to Node 22

Auth0 is retiring the Node.js 18 runtime that custom login code runs on. If your tenant still uses it, you've got until 10 May 2027 to move to Node 22 and test it. Leave it, and Auth0 will eventually move that code for you, tested or not.

Cohash Security Practice November 2026 12 min read 6 chapters 3-question check
part 45 of 45 · Platform releases, explained from scratch
01 Code on Node 18 02 Test in a devtenant 03 Switch by 10 May2027

the ideaTest on Node 22 and switch yourself before Auth0 moves your code.

after reading, you can
  • Spot what in your tenant still runs on Node 18, and which dropdown or Action moves it
  • Spot the Node 22 changes that break Actions, Rules and connection scripts before your users do
  • Plan a switch you can back out of, and move Hooks first, since they stop after 30 April 2027 anyway

If your Auth0 tenant still runs custom code on Node.js 18, you've got a deadline. Auth0 deprecated that runtime on 10 November 2026 and gives tenants that still use it until 10 May 2027 to get onto Node 22. Make the switch yourself, after testing, so Auth0 doesn't make it for you later.

in plain wordsDeadline: 10 May 2027

Auth0 is changing what your login code runs on. Pick the day yourself

Auth0 runs the sign-in for your apps. Many teams add their own code to that sign-in: something that puts a user's role into their token, checks a new sign-up, or looks up passwords in an old database while users are being moved across. That code runs on a version of Node.js, the engine that executes JavaScript, and Auth0 decides which version from your settings. Node.js 18 stopped getting security fixes from its own maintainers in April 2025, and now Auth0 is retiring it too. You have until 10 May 2027 to switch to Node 22 and check nothing broke. Code that's still on Node 18 after that will eventually be moved to a newer engine by Auth0, whether anyone has tested it there or not.

think of it like this

Think of a building that's replacing its old lift motor next spring. The lift keeps running either way. But if your floor had custom buttons wired for the old motor, you want an electrician to check them before the swap, while you still choose the day.

who should care
  • Teams with Auth0 Actions on Node 18
  • Tenants that still run Rules or Hooks
  • Custom database or social connections
  • Anyone using Marketplace Actions
  • Terraform configs that still say node18
chapter 01

Why should anyone outside the identity team care?

10 Nov 2026Auth0 deprecated the Node.js 18 extensibility runtime
10 May 2027Grace period ends for tenants still using Node 18
30 Apr 2025Node.js 18 stopped getting fixes from the Node.js project
5Kinds of custom code affected: Actions, Rules, Hooks, custom DB and custom social scripts

Custom login code is usually a security control. It adds the roles your apps check, blocks sign-ins that shouldn't happen, or decides whether a password from the old user store is right. If that code breaks after a runtime change, logins can fail, or tokens can go out without the claims your apps rely on. The switch is when those failures show up, so pick the day yourself and have someone watching.

Auth0 hasn't published a date for the forced move. Its notice says the Node 18 option will "progressively become unavailable for selection", first for tenants that no longer use it, and that leftover code "will eventually be forced to run on a newer runtime". Removal comes some time after the grace perioddefinitionHow long Auth0 lets tenants still on Node 18 keep using it: until 10 May 2027. Don't treat the last day as the plan. ends. Plan as if the move could happen any day after that.

There's a second clock most notices skip. The Node.js project's own schedule ends support for Node 22 on 30 April 2027, ten days before Auth0's grace period runs out. Node 22 is still what Auth0 recommends, and its changelog, when we read it on 17 November 2026, listed nothing newer for extensibility. So expect another notice like this one. Write the code now so the next switch is a dull afternoon.

what changesHow the Node 18 retirement plays outOnly the switch-and-test step is on your schedule. The rest happen when Auth0 decides.
  1. 01 Code runs on Node 18

    Any Action set to Node 18, plus Rules, Hooks and connection scripts if the tenant settings still say Node 18.

  2. 02 The option starts to vanish

    Node 18 drops out of the runtime menus, first for tenants that no longer use it.

  3. 03 You switch and test

    You deploy a new version of each Action on Node 22. Someone flips the tenant settings in a development tenant first and only touches production once logins there work.

  4. 04 Grace period ends

    Once 10 May 2027 passes, Auth0 starts removing Node 18 for good. It hasn't published a date for the last step, so don't plan around one.

  5. 05 Leftovers get moved for you

    Code still on Node 18 is eventually forced onto a newer runtime. Marketplace Actions whose authors never updated them may lose support.

For engineers: Actions and tenant settings move separately. Each Action version has its own runtime, so you upgrade it by deploying a new version on Node 22, and you can revert to the old version if logins break. The tenant settings work differently. One dropdown moves every Rule and Hook at once, and the other moves every custom database and custom social connection script. Auth0's guide says to change them in a development tenant first and only touch production once everything there passes.

chapter 02

What actually breaks when code moves to Node 22?

side by sideLife on each runtime inside Auth0
Staying on Node 18
  • Upstream security fixes have already stopped
  • The option is disappearing from the menus
  • use npm directive still available
  • Code can write to the filesystem
Moving to Node 22
  • The runtime Auth0 recommends
  • Node.js project support until 30 April 2027
  • No use npm directive
  • No filesystem writes
  • Top-level Action code reused across runs

The changes that touch this switch

deprecatedNode.js 18 extensibility runtime

Deprecated on 10 November 2026. Tenants still using it have a grace period until 10 May 2027, then the end-of-life phase starts.

changedTwo tenant runtime settings

Legacy Extensibility covers Rules and Hooks. The other setting covers custom database and custom social connection scripts. Each change hits every script under it at once.

removedThe use npm directive

Auth0's Node 22 guide says the use npm directive is gone. If your code pulls packages that way, someone has to rewrite it before it moves.

removedFilesystem write access

Disabled on Node 22. Anything that writes a temp file, a cache file or a certificate to disk needs another approach.

changedTop-level Action code is reused

On Node 22 the code at the top of an Action file runs once per instance, and Auth0 can reuse the result across many executions. Anything stored there can outlive the login that set it.

changedA different Can I Require list

Rules, Hooks and connection scripts can only load the module versions on Auth0's Can I Require list for the runtime. The Node 22 list isn't the same as the Node 18 one.

deprecatedMarketplace Actions left on Node 18

Auth0 says a Marketplace integration may lose support if its author never ships a version for a newer runtime. Ask the vendor now, while there's time to find a replacement.

changedAction Modules follow the caller

A module runs in the runtime of the Action that imports it, so a module that's fine from a Node 18 Action can fail from a Node 22 one.

The reused top-level code is the quiet one. People often set up a client or read a value at the top of an Action file. On Node 22 that code runs once per instance and Auth0 can reuse the result across many logins. A top-level variable that holds anything about one user could still be there when the next user signs in. Keep anything per-login inside the handler.

The use npm directive and filesystem writes are easier to spot. Search the code for both before you move anything, because each needs a rewrite on Node 22. Action Modules deserve their own test pass. Auth0 builds a module with its builder runtime but runs it in the runtime of the Action that imports it, so test each importing Action separately.

One admin on Auth0's community forum reported a trap in the legacy sandbox. After switching their tenant to Node 22, they found a Hook could no longer load google-auth-library, though googleapis, which bundles it, was still allowed. An Auth0 community responder called it a known gap in the Node 22 module list and suggested getting the auth client through googleapis. Check every require() in Rules, Hooks and connection scripts against the Node 22 list before you flip the setting.

tableWhere each kind of code gets its runtime. You move Actions one at a time, but a single tenant setting moves the rest in bulk.
Code typeWhere the runtime is setHow to move itDate to watch
ActionsEach Action versionDeploy a new version on Node 2210 May 2027
RulesTenant: Legacy ExtensibilityOne setting moves every Rule10 May 2027, Rules stop 31 Jan 2028
HooksTenant: Legacy ExtensibilitySame setting as RulesHooks stop 30 Apr 2027
Custom database scriptsTenant: Extensibility runtimeOne setting moves every connection10 May 2027
Custom social connectionsTenant: Extensibility runtimeSame setting; Marketplace scripts only via Management API10 May 2027
Marketplace ActionsThe integration's authorInstall the author's newer versionMay lose support

Auth0 runtimes and the dates around this switch

  1. Jan 2025
    Node 22 available in Auth0

    New Actions start defaulting to Node 22, and the tenant runtime setting gets split in two. That's why there are two dropdowns today.

  2. 19 Feb 2025
    Node 12 and 16 deprecated

    Auth0 deprecates the two older runtimes and tells everyone to use Node 22.

  3. 30 Apr 2025
    Node.js 18 end of life

    The Node.js project stops fixing Node 18.

  4. 10 Nov 2026
    Auth0 deprecates Node 18

    Tenants still on Node 18 enter the grace period. The option starts disappearing from the menus from here on.

  5. 30 Apr 2027
    Hooks stop, Node 22 end of life

    Auth0 removes Hooks. The Node.js project stops fixing Node 22 the same day.

  6. 10 May 2027
    Grace period ends

    The end-of-life phase for Node 18 begins.

  7. 31 Jan 2028
    Rules stop

    Auth0 removes Rules.

chapter 03

How do you switch without breaking logins?

before

Before: Node 18 in three places

Some Actions still pin Node 18, and both tenant settings point at it. The deploy pipeline keeps it that way.

Before: Node 18 in three places Some Actions still pin Node 18, and both tenant settings point at it. The deploy pipeline keeps it that way. 01 · ACTIONS 02 · TENANT SETTINGS 03 · SCRIPTS 04 · PIPELINE sets runtime Post-login Action runtime node18 M2M Action runtime node18 Legacy Extensibility Node 18 Extensibility runtime Node 18 Rules and Hooks code read-only Custom DB and social connection scripts Terraform config pins node18 © Cohash · cohash.com
01 · ACTIONS02 · TENANT SETTINGS03 · SCRIPTS04 · PIPELINE Post-login Action: runtime node18 Post-loginAction runtime node18 M2M Action: runtime node18 M2M Action runtime node18 Legacy Extensibility: Node 18 LegacyExtensibility Node 18 Extensibility runtime: Node 18 Extensibilityruntime Node 18 Rules and Hooks: code read-only Rules and Hooks code read-only Custom DB and social: connection scripts Custom DB andsocial connection scripts Terraform config: pins node18 Terraform config pins node18 sets runtime © Cohash · cohash.com
after

After: Node 22 everywhere, tested first

Every deployed Action runs on Node 22, both settings say Node 22, and the pipeline config says node22 too, so a routine deploy doesn't bring Node 18 back.

After: Node 22 everywhere, tested first Every deployed Action runs on Node 22, both settings say Node 22, and the pipeline config says node22 too, so a routine deploy doesn't bring Node 18 back. 01 · ACTIONS 02 · TENANT SETTINGS 03 · SCRIPTS 04 · PIPELINE sets runtime Post-login Action new version, node22 M2M Action new version, node22 Legacy Extensibility Node 22 Extensibility runtime Node 22 Hooks moved to Actions before 30 Apr 2027 Custom DB and social tested in dev Terraform config node22 in code © Cohash · cohash.com
01 · ACTIONS02 · TENANT SETTINGS03 · SCRIPTS04 · PIPELINE Post-login Action: new version, node22 Post-loginAction new version,node22 M2M Action: new version, node22 M2M Action new version,node22 Legacy Extensibility: Node 22 LegacyExtensibility Node 22 Extensibility runtime: Node 22 Extensibilityruntime Node 22 Hooks moved to Actions: before 30 Apr 2027 Hooks moved toActions before 30 Apr 2027 Custom DB and social: tested in dev Custom DB andsocial tested in dev Terraform config: node22 in code Terraform config node22 in code sets runtime © Cohash · cohash.com

The switch, from inventory to production

  1. 01
    List what runs on Node 18

    Open each Action and write down its runtime, or pull it from the runtime field in your Terraform config. Check both tenant dropdowns too. For custom social connections, use the Management API query from Auth0's guide that filters on strategy oauth1 and oauth2.

  2. 02
    Read the code for Node 22 traps

    Search for the use npm directive and for filesystem writes. Move per-login data out of top-level variables. Check every require() in Rules, Hooks and connection scripts against the Node 22 Can I Require list.

  3. 03
    Upgrade Actions one at a time

    Create a new version of each Action with Node 22 as its runtime and deploy it. Watch the logs for a day. If logins break, revert to the previous version from the Action's version history.

  4. 04
    Flip the tenant settings in development

    Do it in a development tenant first: Settings, Advanced, Extensibility, and set both runtimes to Node 22. Then have someone sign in through every connection and app you've got, custom database and social ones included. If anything breaks, you've found it before a customer did.

  5. 05
    Repeat in production in a quiet window

    Make the same change with someone watching the tenant logs. Don't count on switching back for long: Auth0 says the Node 18 option disappears first for tenants that no longer use it.

  6. 06
    Change the deploy code too

    Set runtime to node22 on Terraform auth0_action resources and sandbox_version to 22 on auth0_tenant. If the code still says Node 18, the next deploy can set it back.

  7. 07
    Treat Hooks as a migration

    Hooks stop running after 30 April 2027 whatever runtime they use. A Hook that breaks on Node 22 can't be edited, because Hooks code has been read-only since November 2024, so move it to an Action now.

chapter 04

What should each person do now?

What to do now, by who you are

Business ownerthis month
  • Ask whoever runs Auth0 whether anything still uses Node 18, and get a switch date well before 10 May 2027.
  • Ask which Marketplace integrations you rely on, and whether each has a Node 22 version yet.
  • Make sure the Hooks migration has its own plan. Hooks stop after 30 April 2027, before the runtime deadline.
Identity and IT teamthis quarter
  • Export the tenant into source control. Then you've got one list of every runtime setting and Action runtime instead of a Dashboard hunt.
  • Switch a development tenant to Node 22 first and run test logins through every connection.
  • Pick a production window and decide in advance what you'll do if a Rule or Hook fails.
  • Update the Terraform config in the same change.
Developersbefore each switch
  • Rip out use npm and any filesystem writes. Neither works on Node 22.
  • Move per-login values out of top-level variables in Actions.
  • Check every require() in the legacy sandbox against the Node 22 Can I Require list.
  • Ship each Action upgrade as a new version, so you can roll back just that one if it breaks.
  • Test each Action that imports an Action Module, because the module runs on the caller's runtime.
Security and auditafter the switch
  • Confirm nothing in the tenant or the deploy code still says Node 18.
  • Record the change, the test logins and who approved it.
  • Add 30 April 2027 to the risk register. That's when the Node.js project stops fixing Node 22 too.
chapter 05

How do you make the next runtime change routine?

Habits that make the next notice cheap

  1. 01
    Keep the tenant in source control

    With Terraform, every runtime value sits in a file someone reviews. Finding every Node 18 reference becomes a text search instead of a Dashboard tour.

  2. 02
    Keep a test tenant that looks like production

    Same connections, same Actions, a few test users per connection. Run the same sign-ins after every change and compare the tokens.

  3. 03
    No user data at the top of an Action

    Anything about the person signing in lives inside the handler. Top-level code only sets up things that are safe to share, like a client object.

  4. 04
    Keep dependencies few and current

    Stick to maintained packages, run npm audit, and take the latest version where you can, which is what Auth0's coding guidance asks for too. Every package you drop is one less thing to break on the next runtime.

  5. 05
    Get off Rules and Hooks

    Hooks stop after 30 April 2027 and Rules on 31 January 2028. Once everything's an Action, each piece changes runtime on its own and can be rolled back on its own.

If the switch goes wrong

The usual failure is a burst of failed logins, or tokens missing a claim, right after a runtime change. Work through these phases in order, and fix the cause before you try again.

  1. 01Stop the damagefirst 15 minutes
    • Was it an Action? Revert it to the previous version from its version history, and logins go back to how they were.
    • If a tenant setting caused it, set it back to Node 18 if the option is still there.
    • If Node 18 is gone, decide with the security team whether the failing Rule or Hook can be disabled safely. Disabling a check can let people in without it.
    • Warn the support desk. Users will call about failed logins, and someone there should know why.
  2. 02Find the causefirst day
    • Read the tenant logs for failed logins, then the Action's execution logs. Don't sit on it: Auth0 only keeps execution logs for 10 days.
    • Look for the usual suspects: a module missing from the Node 22 list, use npm, a filesystem write, or shared top-level state.
    • Test any Action Module under a Node 22 Action. The module runs on whatever runtime the caller uses, so it can break even though nobody touched it.
  3. 03Fix and retestthis week
    • Fix the Action in the development tenant and rerun the full set of test logins.
    • A broken Rule or Hook can't be patched, because nobody can edit their code. The fix is a replacement Action.
  4. 04Report and learnafter the fix
    • If anyone got access they shouldn't have, treat it as a security incident and follow your usual reporting.
    • Write down what broke and add a test login that would've caught it, so the next switch catches it for you.
chapter 06

What does this look like in a real tenant?

Three typical Auth0 tenants

01 Login A 02 Top-levelcache holds A's org 03 Handler-onlydata fresh each login 04 Login B token
scenario 01Medium risk
A SaaS product with a few post-login Actions
the setup
A product team has four Actions, all created on Node 18. One of them builds an API client at the top of the file and also keeps the last user's organisation ID there to save a lookup.
what happens
The runtime change itself goes fine. Because Node 22 reuses top-level code across executions, the cached organisation ID can carry into the next login on the same instance, and a token could carry the wrong organisation.
what to do
Move the organisation lookup inside the handler, then upgrade each Action as a new version on Node 22 and compare tokens before and after.
01 Customerlogin 02 Login script untested on Node 22 03 Dev tenanttest Node 22 04 Old userstore
scenario 02High risk
A retailer partway through a user migration
the setup
A retailer is moving customers off an old user store with an Auth0 custom database connection. The login and get-user scripts run on the tenant's Extensibility runtime, still set to Node 18.
what happens
Changing that one dropdown moves every connection script at once. If the login script uses a package that isn't on the Node 22 list, every customer who hasn't been migrated yet can't sign in until someone fixes it.
what to do
Copy the connection into a development tenant, switch it to Node 22 and sign in as a few not-yet-migrated test users. Fix the script there first. The change to custom DB imports on 20 January 2027 is worth testing in the same pass.
01 Admin request 02 Frozen Hook missing package 03 New Action Node 22 04 Google API
scenario 03High risk
An enterprise with frozen Hooks
the setup
An enterprise still has Hooks from an older admin extension. One of them loads google-auth-library to reach a Google API. Nobody can edit the Hook's code, because Hooks became read-only in November 2024.
what happens
The legacy runtime goes to Node 22 and the Hook can no longer load the package. Nobody can patch the Hook, so the feature stops until the setting goes back to Node 18, if that's still offered.
what to do
Find this in a development tenant first. Then replace the Hook with an Action now. Hooks stop after 30 April 2027 anyway, so the runtime switch only moves that work forward.

We run Auth0 runtime switches and Rules and Hooks migrations, and we compare tokens before and after each step so you can see that nothing changed for users. Our Auth0 page explains how we work. If you'd rather keep it in-house, you can hire Auth0 engineers to join your team, or start with an identity assessment that lists what your tenant still runs. The other Auth0 deadlines are in our posts on Rules and Hooks end of life and the custom DB import change.

key takeaways

What to take from this

  1. 01

    Node 18 is on its way out of Auth0. Pick your own day before 10 May 2027 to move everything to Node 22.

  2. 02

    Actions move one version at a time with a way back. Tenant settings move every Rule, Hook or connection script at once.

  3. 03

    Before switching, hunt for use npm, filesystem writes, user data in top-level variables and modules missing from the Node 22 list. Each of those can bite on Node 22.

  4. 04

    Hooks stop after 30 April 2027 and can't be edited. Replace them with Actions instead of only switching their runtime.

  5. 05

    Node 22 loses Node.js project support on 30 April 2027 as well, so keep the tenant in code and expect the next notice.

platforms in this noteAuth0 →
fact-checked November 2026 against vendor and official documentation · where to go next
  1. How Cohash delivers Auth0: scope, roles and architecture
  2. Hire vetted Auth0 engineers
  3. Customer identity
  4. Book a 30-minute working session with a senior engineer
01When does Auth0 stop supporting Node 18?

Auth0 deprecated it on 10 November 2026, and tenants still using it have until 10 May 2027. After that Auth0 starts the end-of-life phase and eventually removes Node 18 completely. Don't leave it for the last week.

02What happens if we do nothing?

Auth0 says code still on Node 18 will eventually be forced onto a newer runtime. It hasn't given a date for that. The risk is that the move happens on a day you didn't pick, with code nobody tested on Node 22.

03Which parts of Auth0 does this affect?

All five kinds of custom code: Actions, Rules, Hooks, custom database and custom social connection scripts. Actions get switched one at a time. Rules and Hooks follow the Legacy Extensibility setting, and custom database and social connection scripts follow the other dropdown, both under Settings, Advanced, Extensibility. Change either and every script under it moves at once.

04Do we still need to do anything for Hooks if they stop in April anyway?

Hooks stop running after 30 April 2027, ten days before the runtime grace period ends. Switching the legacy runtime still affects them while they run. The better use of the time is replacing each Hook with an Action.

05Can we switch back to Node 18 if something breaks?

For an Action, yes: revert to the previous version, which keeps its old runtime. For the tenant settings, only while Node 18 is still offered, and Auth0 says it disappears first for tenants that no longer use it. Test in a development tenant so you don't need to.

06How long will Node 22 last?

Node 22 is the runtime Auth0 recommends today. The Node.js project's schedule ends its support on 30 April 2027, so another Auth0 runtime change is likely. Keep the tenant in code so the next switch is quick.

07One of our Marketplace integrations still runs on Node 18. What should we do?

Ask the author for a version that targets a newer runtime. Auth0 says Marketplace Actions that depend on Node 18 and get no update may become unsupported. If it's a social connection, its script can only be changed through the Management API.

next track

That's the end of this track.

Next up: running enterprise platforms well. ERP, CRM and ITSM work that holds up after go-live.

  1. 01HashiCorp Vault 2.2 explained: TPM login, post-quantum PKI and the October fixes
  2. 02Upgrading to SailPoint IdentityIQ 9.0: what breaks and what to fix first
  3. 03Terraform 1.17 explained: what's new, who it touches and how we'd upgrade
  4. 04BeyondTrust Remote Support zero-day: patch it, then check who got in
  5. 05Patch PHP and Node.js this week: what broke and who's exposed
  6. 06OpenShift support dates through 2027: which clusters run out first and how to plan the upgrades
  7. 07Oracle's October security patches: what to fix first in EBS, PeopleSoft and Access Manager
  8. 08Oracle's eMudhra alert now covers Database Server: patch, then test what breaks
  9. 09Delinea Secret Server auth bypass: why the FIDO2 hotfix isn't enough
  10. 10IBM Verify Access flaws let attackers run code without a login: patch to 11.0.3.2
  11. 11Foundry Workflows retire on December 1. We'd start moving yours to Agent Framework now
  12. 12Vertex AI is retiring text-embedding-005 and three other embedding models: how to re-embed before search breaks
  13. 13dbt drops v1.3 to v1.7 from its platform on January 31, 2027: get pinned jobs onto a release track before they're deleted
  14. 14Brotli CVE-2026-111497 is now on CISA's exploited list, and you probably run more copies than you think
  15. 15Auth0 moved the Rules and Hooks deadline: Hooks stop on 30 April 2027, Rules on 31 January 2028
  16. 16Still on Okta Classic Engine? Three features stop working on March 5, 2027, and two of them block the upgrade
  17. 17Patched GitLab, still exposed: the CI regex bug CISA lists as exploited, and the Ruby step people miss
  18. 18Patched Ivanti Connect Secure in October? Two more exploited bugs, and the AD cleanup
  19. 19Patch roundup, week of Oct 26: upgrade Secret Server today, then work down the list
  20. 20UiPath 2023.10 support has run out and 2024.10 is next. What we'd upgrade first
  21. 21Password Safe 24.3 runs out of support in December, and 26.3 is still one upgrade away
  22. 22Upgrade Entra Connect Sync before April 2027 and move users off Microsoft's SMS codes
  23. 23Chrome drops XSLT on 17 November. What breaks in InterSystems, and the fix for your version
  24. 24Agent Builder, Evals and saved prompts shut on 30 November. Here's what to pull out first
  25. 25BeyondTrust Remote Support and PRA 24.3 lose support in November, and there's no one-step upgrade
  26. 26OpenShift 4.19 is running out of support. Do you park on 4.22 or keep going to 5.0?
  27. 27Terraform Enterprise 2.1 moves VCS ingress into your agents. What to change before October 2027
  28. 28Mule 4.12 Edge leaves standard support this month. Upgrade to 4.13 before CloudHub does it for you
  29. 29RSA SecurID primary support ends in stages from December. Here's how you get to 8.9
  30. 30Delinea Secret Server login bypass: why 12.2.7 won't save you from this 9.9
  31. 31Entra password reset won't take directory phone numbers from February 2027. Who gets stuck?
  32. 32Linux kernel CVE-2026-98432: why switching off MPTCP won't save you, and what to patch
  33. 33Patch roundup, week of Nov 2: fix Linux and WS_FTP first, then work down the list
  34. 34Auth0's lazy migration changes on 20 January 2027, and half-imported users won't fix themselves
  35. 35Your Databricks AI Functions need Runtime 17.3 LTS by January 2027, even if 15.4 is still supported
  36. 36SonicWall's SSL VPN bug lets a valid password skip SAML and your MFA
  37. 37Oversized Auth0 profiles can break logins after 4 March 2027. Here's how to find yours
  38. 38You patched your Cisco email gateway. One email can still take it over.
  39. 39Barracuda email gateways are being hacked through their admin page: patch and lock it down
  40. 40Citrix NetScaler's November fixes: one flaw hits every box, and Console has a login bypass
  41. 41Fortinet's November fixes: FortiMail, FortiManager and FortiAuthenticator flaws that need no login
  42. 42November's Microsoft patches: do the domain controllers and Outlook first
  43. 43SAP's November patches: four flaws that need no password
  44. 44GitLab's off-cycle Git fix: a merge request can run code on Gitaly, and source installs need two patches
  45. 45Auth0 is pulling Node 18 out from under your login code. Here's how to move it to Node 22
all learning tracks →
Time to upgrade or move No newenvironments Suspended Decommission… Nov 2026 Oct 2027
Engineering · 15 minDataverse for Teams is going away: what to keep, move or let go before September 2027

Most teams still have time to upgrade or move their apps. After September they don't.

read next
next step

Tell us what you're running. We'll tell you what we'd do first.

A 30-minute working session with a senior engineer. No slides.

useful to bring
  • The platform and the version you're on
  • Where you need to get to, and by when
  • What's custom: rules, plugins, integrations
  • Any audit finding or deadline driving it