Agent successfully upgraded to 9.5.0-SNAPSHOT without available link/binary .

[kishorkumar-qasource]

Kibana Build details:

VERSION: 9.5.0-SNAPSHOT
BUILD: 104406
COMMIT: 93b0b9d110c75823614e8f77cbb9d60cdbd3f806

Preconditions:

1. 9.5.0-SNAPSHOT Kibana cloud environment should be available.
2. An agent version less than 9.5.0 should be available.
3. Target upgrade version 9.5.0-SNAPSHOT should not available as an agent binary in Settings.

Steps to Reproduce:

1. Navigate to the Fleet > Agents tab.
2. Select an agent running a version lower than 9.5.0.
3. Open the Actions menu for the selected agent.
4. Click on Upgrade Agent.
5. Add version as 9.5.0-SNAPSHOT.
6. Observe that the agent is successfully upgraded despite the missing binary availability validation.

Expected Result:

If the 9.5.0-SNAPSHOT binary is not available, the upgrade should be blocked and the upgrade state should be shown as Upgrade Failed.

Screen Capture:

Screen.Recording.2026-06-08.at.6.17.31.PM.mov

[infra-vault-gh-plugin-prod]

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

[kishorkumar-qasource]

Hi @arvindersingh-qasource Kindly review this.

[arvindersingh-qasource]

Secondary review for this ticket is done.

[cmacknz]

Maybe I'm missing it, but 9.5.0-SNAPSHOT should be available from the default binary source, so I'm not sure why this fails.

Besides not following that, to prevent the upgrade Kibana would have to reach out to the artifact source before sending the action to the agent, which could be done but might fail in self-managed or air gapped where Kibana does not otherwise need this URL to be reachable.