# Remediation Handoff: CVE-2026-14574

## Summary

NVD: In Eclipse Theia versions 0.7.0 and up until including 1.73.1, the PreferenceUtils.merge function in @theia/core recursively merges preference values without rejecting prototype-related keys (__proto__, constructor, prototype). NVD: Because this function is invoked by PreferenceServiceImpl.doResolve for every preference resolution across scopes (default, user, workspace, folder), a crafted preference value in a workspace settings file (.theia/settings.json or .vscode/settings.json) can... OSV: In Eclipse Theia versions 0.7.0 and up until including 1.73.1, the PreferenceUtils.merge function in @theia/core recursively merges preference values without rejecting prototype-related keys (__pr

## Why it matters

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

## Affected context

* Vendor: eclipse
* Product: theia
* Component: unknown
* Version / CPE / PURL: unknown

## Remediation context

* Recommended route: vendor_patch_or_mitigation
* Vendor/advisory reference: official_reference_present
* Patch status: requires_confirmation
* Fixed version: unknown
* References: https://github.com/eclipse-theia/theia/security/advisories/GHSA-f3w9-qfw3-xr32, https://gitlab.eclipse.org/security/cve-assignment/-/work_items/157, https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/567, https://gitlab.eclipse.org/security/vulnerability-reports/-/work_items/567

## 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-14574 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.