Api-Token — CraftedSignal Threat Feed

Tekton Pipelines Git Resolver API Token Leak via User-Controlled ServerURL

hello@craftedsignal.io — Wed, 22 Apr 2026 12:00:00 +0000

A vulnerability exists in Tekton Pipelines’ git resolver (versions v1.0.0 through v1.10.0) where the system-configured Git API token is sent to a user-controlled serverURL when the user omits the token parameter. This allows a malicious tenant with TaskRun or PipelineRun create permissions to exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing serverURL to an attacker-controlled endpoint. The attacker can then use this token to gain unauthorized access to private repositories, potentially exposing source code, secrets, and CI/CD configurations. This vulnerability is similar to GHSA-j5q5-j9gm-2w5c, where credentials could be exfiltrated. The vulnerability resides in the ResolveAPIGit() function within pkg/resolution/resolver/git/resolver.go.

Attack Chain

Attacker gains permission to create TaskRuns or PipelineRuns within a Tekton Pipelines namespace.
Attacker crafts a malicious TaskRun or PipelineRun configuration.
The configuration specifies the git resolver in API mode.
The configuration omits the token parameter but includes a serverURL pointing to an attacker-controlled endpoint.
Tekton Pipelines executes the TaskRun or PipelineRun, triggering the git resolver.
The ResolveAPIGit() function retrieves the system-configured Git API token using getAPIToken().
The function creates an SCM client pointed at the attacker-controlled serverURL with the system token as an Authorization header.
Subsequent API calls from the resolver to the attacker-controlled URL transmit the system token, allowing the attacker to capture it.

Impact

Successful exploitation allows an attacker to exfiltrate the system Git API token (GitHub PAT, GitLab token, etc.). The exfiltrated token can be used to access private repositories, potentially leading to the exposure of sensitive information like source code, secrets, and CI/CD configurations. This can lead to supply chain compromise, data breaches, or other unauthorized activities. All Tekton Pipeline instances running versions v1.0.0 through v1.10.0 are potentially vulnerable if a system-level API token is configured.

Recommendation

Do not configure a system-level API token in the git resolver ConfigMap. Instead, require all users to provide their own tokens via the token parameter, as suggested in the advisory’s workaround section.
Restrict TaskRun creation to limit which users or ServiceAccounts can create TaskRuns and PipelineRuns that use the git resolver, as recommended in the advisory’s workaround section.
Apply NetworkPolicy to the tekton-pipelines-resolvers namespace to restrict outbound traffic to known-good Git servers only, mitigating the risk of token exfiltration to arbitrary serverURL values.

Directus Aggregate Query Vulnerability Allows Disclosure of Concealed Data

hello@craftedsignal.io — Sat, 04 Apr 2026 06:13:57 +0000

Directus versions prior to 11.17.0 contain a vulnerability where aggregate functions, such as min and max, when applied to fields with the conceal special type, incorrectly return raw database values instead of the masked placeholder. This affects authenticated users who have read access to the affected collection, enabling them to extract concealed field values via groupBy aggregate queries. This vulnerability allows for the extraction of sensitive information, such as static API tokens and two-factor authentication secrets stored in directus_users, enabling account takeovers and 2FA bypass. The vulnerability was reported on April 4, 2026, and is identified as CVE-2026-35442. Defenders should prioritize upgrading Directus instances to version 11.17.0 or later to mitigate this risk.

Attack Chain

Attacker authenticates to a vulnerable Directus instance with valid user credentials.
Attacker identifies a collection containing fields with the conceal special type, such as directus_users.
Attacker crafts an aggregate query using functions like min or max on the concealed field and includes a groupBy clause. Example: SELECT min(secret_field) FROM collection GROUP BY other_field.
The Directus server processes the aggregate query but fails to properly apply the masking logic to the nested results.
The server returns the raw, unmasked values of the concealed field in the aggregate query response.
The attacker extracts static API tokens and TOTP seeds from the returned data.
Attacker uses the extracted API tokens to authenticate as other users, including administrators, bypassing username/password requirements.
Attacker uses the extracted TOTP seeds to bypass two-factor authentication for other users, gaining unauthorized access to their accounts.

Impact

Successful exploitation of this vulnerability can lead to complete account takeover, including administrative accounts. Two-factor authentication mechanisms can be bypassed, invalidating this security control. The number of affected organizations depends on the adoption rate of Directus, but all instances running versions prior to 11.17.0 are vulnerable. If the attack succeeds, attackers gain full control over the Directus instance and associated data, potentially leading to data breaches, service disruption, and reputational damage.

Recommendation

Upgrade Directus to version 11.17.0 or later to patch the vulnerability (CVE-2026-35442).
Implement a Web Application Firewall (WAF) rule to detect and block aggregate queries targeting concealed fields in sensitive collections. See the Sigma rule example for guidance.
Monitor Directus application logs for unusual aggregate query patterns, especially those involving groupBy and functions like min or max.