Case · DiggingBeagle record

An agent selected a patched skill but executed an old loaded handle in a benchmark

SkillLifeBench exposes a mismatch between the version an agent says it chose and the executable skill still cached by its runtime.

Scope

Controlled skill-lifecycle scenarios, not a count of exploited real installations. Outcomes depend on the benchmark harness and simulated package states.

Assessment profile

Assessment method
Setting
evaluation
Exploitation
demonstrated
Evidence
Grade B
Remediation
mitigation available
AI role
AGAINST AI
Basis and provenance

SkillLifeBench provides a controlled lifecycle regression, without identifying live victims or a particular commercial platform patch. Impact remains unrated because the scoped record does not establish a calibrated severity-to-impact-band mapping.

Assessed Oct 31, 2026 using diggingbeagle.assessment/1.

At a glance

Mechanism and trust boundary

  1. 01

    Step

  2. 02

    Step

  3. 03

    Step

Timeline

  1. Oct 29, 2026
    disclosure

    Public disclosure

Claims & evidence

CLM-C26-SKILLLIFEBENCH-STALE-HANDLE-1SkillLifeBench documents a controlled case in which an agent chose patched skill v1 but executed a stale v0 handle with an unsafe filesystem capability.supported

Basis: reported finding

Link to claim

Implications

A correct version decision in text does not prove the executing capability or loaded artifact has been revoked.

Controls and mitigations

  • Bind tool calls to a current version hash and invalidate loaded handles during updates; test actual call targets after an upgrade.

Unknowns and contradictions

  • The share of real agent systems retaining stale tool handles is not established.
  • Update mechanisms that forcibly rebind and revoke existing handles need independent testing.

Sources and citation

Material revision history

  1. Oct 31, 2026 · Canonical change recorded · new in release · revision 208