# CVE-2026-113971: CVE-2026-113971

Status: published. Published: 2026-11-09. Updated: 2026-11-09.

This issue was addressed by restricting options offered on a locked device. This issue is fixed in iOS 18.7.12 and iPadOS 18.7.12, iOS 26.5 and iPadOS 26.5. An attacker with physical access may be able to pair a device with an AirPlay receiver from the lock screen.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Apple / iOS and iPadOS: ≥ 0; < 18.7.12 (affected, custom); ≥ 0; < 26.5 (affected, custom). Source: CNA: apple

## Severity and prioritization

- CVSS 3.1: 3.5 (low); CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N; source: ADP: CISA-ADP

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable no; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-284

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://support.apple.com/en-us/127110 (CNA: apple)

- https://support.apple.com/en-us/149717 (CNA: apple)

## Provenance

- CNA: apple: https://www.cve.org/CVERecord?id=CVE-2026-113971; retrieved 2026-11-09; source updated 2026-11-09

Revision: 989be5d8a492e13575975c0d04af575e3ab0d82053a18d9f11c90b25156935d4

Canonical: https://y2.dev/cve/CVE-2026-113971

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.