a2a-dotnet EUVD-2026-110071

Exploitation requires the ability to submit concurrent/overlapping task requests (SendMessage or SendStreamingMessage) targeting the SAME TaskId against an a2a-dotnet A2AServer instance, which per the CVSS vector needs low-privilege authenticated access (PR:L). The flaw lives in TaskProjection.ApplyStatus and the associated background-cancellation registration in A2AServer.cs, where the fix PR replaces an unsynchronized GetOrAdd/CTS pattern with lock-guarded (AcquireTaskLockAsync) reservation and release - indicating the trigger is concurrent manipulation of a single task's status/cancellation state. Limiting factors: the attacker must win a narrow timing window (race condition, CWE-362), must be authenticated at a low privilege level, and the affected code is present only up to version 1.0.0-preview3. The available sources do not describe a specific deployment configuration toggle required to trigger it beyond concurrent same-TaskId requests.

This is a medium-severity, low-urgency issue rather than an emergency. The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L, score 5.3) describes a network-reachable but privilege-requiring (PR:L) flaw with no confidentiality impact and only low integrity and availability impact - consistent with a concurrency bug that corrupts task state rather than one that leaks data or grants code execution. No EPSS score was provided, the CVE is not listed in CISA KEV, and no proof-of-concept or exploit reference appears in the input, so there is no public exploit identified at time of analysis. The vuln.today decision label is 'this_month' (not act_now/emergency), which aligns with the modest impact metrics. One conflict should be flagged: the input Tags include 'Information Disclosure,' but the CVSS vector sets VC:N (no confidentiality impact) and instead shows VI:L/VA:L - the labeled impact category and the scored impact disagree; treat the confidentiality framing as unverified and prefer the integrity/availability reading. Note also that CWE-362 (race condition) inherently requires winning a timing window, which the input vector models as AT:N/AC:L but which realistically limits reliable exploitation. Overall: a genuine but low-priority defect, appropriate for routine patching rather than crisis response.

A low-privilege authenticated client issues concurrent or overlapping SendMessage/SendStreamingMessage requests for the same TaskId, racing the TaskProjection.ApplyStatus logic and the background-cancellation bookkeeping in A2AServer. Winning the timing window can leave task status inconsistent or orphan the per-task CancellationTokenSource, degrading the integrity and availability of task processing. No public exploit code was identified in the provided sources; the only code artifact is the pending fix PR #453.