Disclosed weakness · no CVE recorded

GitHub Agentic Workflows startup logged API-key prefixes

GitHub · GitHub Agentic Workflows · MCP startup scripts

First documented disclosure · Review checkpoint

Summary

MCP startup scripts wrote API-key prefixes to logs.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reviewed sources describe a correction or controlled reproduction; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Diagnostic logging included the beginning of the configured API keys.

Conditions required

A workflow uses the affected startup scripts and another party can read its logs.

Potential impact

A prefix of an API credential could be disclosed. The report does not establish disclosure of the complete key or resulting authentication access.

Affected versions and configurations

The reviewed upstream report does not establish a complete affected-release range.

Fix and mitigation status

1.3.1 contains the correction and is marked prerelease. A corresponding stable release is unverified.

Practical next steps

Use the reviewed prerelease or patch, and assess log exposure according to the sensitivity of the disclosed credential prefix.

Operating lesson

Exclude credential fragments from routine diagnostics.

Evidence and limits

The fix covers both MCP startup scripts and retains the key as an intentional GitHub Actions output. Tagged verification: the reviewed MCP scripts startup file writes the key only to the declared Actions output and omits prefix logging.

Sources