# Remediation Handoff: CVE-2026-86462

## Summary

NVD: Apache Airflow FAB provider: changing a user's password through the Admin user-edit PATCH endpoint does not invalidate that user's existing database-backed sessions. NVD: An attacker who already holds a copy of the victim's session cookie keeps full access as that user after the password change, so the password reset does not evict them. NVD: Affects deployments using the FAB auth manager with database-backed sessions; an administrator (or the user themselves) performing a routine password change is the trigger, and no attacker interaction with the endpoint is needed.

## Why it matters

CVSS severity is CRITICAL with score 9.1. EPSS percentile is 0.55236. KEV status is not listed in KEV. Use this as a defensive priority handoff, not as an execution instruction.

## Affected context

* Vendor: apache
* Product: apache-airflow-providers-fab
* Component: unknown
* Version / CPE / PURL: unknown

## Remediation context

* Recommended route: vendor_patch_or_mitigation
* Vendor/advisory reference: official_reference_present
* Patch status: confirmed
* Fixed version: 3.9.0
* References: https://github.com/apache/airflow/pull/72657, https://lists.apache.org/thread/7sr4sggfv5fhhl3qgphcq0rlhg81do1s, https://lists.apache.org/thread/7sr4sggfv5fhhl3qgphcq0rlhg81do1s?users@airflow.apache.org

## Human checklist

* Confirm whether the listed product or package is present.
* Confirm affected version.
* Review vendor advisory or official source.
* Confirm patch, fixed version, mitigation, workaround, or monitor-only decision.
* Confirm exposure.
* Document remediation status.

## Safe AI / Codex handoff

* Goal: Prepare a defensive remediation plan for CVE-2026-86462 using only provided public-safe source context and any separate repo context supplied by the user.
* Allowed actions: summarize vendor guidance, prepare a defensive remediation plan, identify affected dependencies only when repo context is separately provided by the user, suggest tests and validation steps, document human verification questions
* Disallowed actions: generate offensive code, provide payloads, scan external targets, change production systems, merge or deploy changes, create GitHub issues or pull requests without explicit separate approval
* Acceptance criteria: Affected product or dependency presence is confirmed by a human., Affected version is confirmed or marked not applicable., Official advisory or source reference is reviewed., Patch, fixed version, mitigation, workaround, or monitor-only decision is documented., Validation steps are proposed without external scanning or production mutation.
* Human approval required: true

## Safety note

This handoff is for defensive triage and remediation planning only. It excludes offensive procedure, payload material, external target scan guidance, and auto-remediation.