How severe is GHSA-wjxp-xrpv-xpff?

GHSA-wjxp-xrpv-xpff has a CVSS score of 7.7/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-wjxp-xrpv-xpff?

GHSA-wjxp-xrpv-xpff affects the following packages: github.com/tektoncd/pipeline (Go), github.com/tektoncd/pipeline (Go), github.com/tektoncd/pipeline (Go), github.com/tektoncd/pipeline (Go), github.com/tektoncd/pipeline (Go). Ecosystems affected: Go.

How do I fix GHSA-wjxp-xrpv-xpff?

Update github.com/tektoncd/pipeline to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjxp-xrpv-xpff is resolved across your whole dependency graph.

How do I detect GHSA-wjxp-xrpv-xpff in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tektoncd/pipeline. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-wjxp-xrpv-xpff if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-wjxp-xrpv-xpff?

O3 pinpoints whether GHSA-wjxp-xrpv-xpff is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-wjxp-xrpv-xpff actively exploited in the wild?

No public exploit code has been indexed for GHSA-wjxp-xrpv-xpff yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-wjxp-xrpv-xpff published, and has it been updated?

GHSA-wjxp-xrpv-xpff was published on April 21, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

GHSA-wjxp-xrpv-xpff

HIGH

GHSA-wjxp-xrpv-xpff is a high-severity (CVSS 7.7) vulnerability in github.com/tektoncd/pipeline. O3 Security confirms whether GHSA-wjxp-xrpv-xpff is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Tekton Pipelines: Git resolver API mode leaks system-configured API token to user-controlled serverURL

Also known asCVE-2026-40161GO-2026-5711

Published

Apr 21, 2026

Updated

Jun 25, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Jun 25, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

5 pkgs affected

🐹github.com/tektoncd/pipeline🐹github.com/tektoncd/pipeline🐹github.com/tektoncd/pipeline🐹github.com/tektoncd/pipeline🐹github.com/tektoncd/pipeline

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

The Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled serverURL when the user omits the token parameter. A tenant with TaskRun or PipelineRun create permission can exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing serverURL to an attacker-controlled endpoint.

Details

The git resolver's ResolveAPIGit() function in pkg/resolution/resolver/git/resolver.go constructs an SCM client using the user-supplied serverURL and a token obtained via getAPIToken().

When the user provides serverURL but omits the token parameter:

getSCMTypeAndServerURL() reads serverURL directly from user params (params[ServerURLParam]) with no validation against the system-configured URL.
secretRef is set to nil because the user did not provide a token parameter.
getAPIToken(ctx, nil, APISecretNameKey) is called. It detects apiSecret == nil, creates a new secretCacheKey, and populates it from the system-configured secret (conf.APISecretName / conf.APISecretNamespace / SYSTEM_NAMESPACE).
clientFunc(scmType, serverURL, string(apiToken)) creates an SCM client pointed at the attacker-controlled URL with the system token. The SCM factory sets the token as an Authorization header on the HTTP client.
All subsequent API calls (Contents.Find, Git.FindCommit) carry the system token to the attacker URL.

Impact

The system Git API token (GitHub PAT, GitLab token, etc.) is exfiltrated to an attacker-controlled endpoint. This token typically has read access to private repositories containing source code, secrets, and CI/CD configurations.

This follows the same threat model as GHSA-j5q5-j9gm-2w5c (published March 2026): a namespace-scoped tenant with permission to create TaskRuns exploits the git resolver to exfiltrate credentials. The prior advisory involved reading the resolver pod's ServiceAccount token via path traversal. This finding involves redirecting the system Git API token via serverURL.

Patches

Fixed in:

v1.0.2 (release-v1.0.x branch)
v1.3.4 (release-v1.3.x branch)
v1.6.2 (release-v1.6.x branch)
v1.9.3 (release-v1.9.x branch)
v1.11.1 (release-v1.11.x branch)

The fix validates that when serverURL is user-provided and differs from the system-configured server URL, the user must also provide their own token parameter. Using the system token with a non-system server URL is rejected.

Workarounds

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.
Restrict TaskRun creation — limit which users or ServiceAccounts can create TaskRuns and PipelineRuns that use the git resolver.
Network egress policies — apply NetworkPolicy to the tekton-pipelines-resolvers namespace to restrict outbound traffic to known-good Git servers only.

Affected Versions

All releases from v1.0.0 through v1.10.0, including all patch releases. The API mode of the git resolver has been present since the resolver was introduced.

Releases prior to v1.0.0 are not affected because the git resolver either did not exist or did not have API mode.

Acknowledgments

This vulnerability was reported by Koda Reef (@kodareef5), who provided a detailed analysis and proof-of-concept. Thank you!

References

Prior advisory: GHSA-j5q5-j9gm-2w5c
Related: #9608 (deprecate api-token-secret-namespace)
Related: #9609 (SubjectAccessReview for resolver secrets)

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.0.0&&< 1.0.2	1.0.2
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.2.0&&< 1.3.4	1.3.4
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.4.0&&< 1.6.2	1.6.2
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.7.0&&< 1.9.3	1.9.3
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.10.0&&< 1.11.1	1.11.1

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/tektoncd/pipeline. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/tektoncd/pipeline to 1.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wjxp-xrpv-xpff is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-wjxp-xrpv-xpff is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wjxp-xrpv-xpff. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The Tekton Pipelines git resolver in API mode sends the system-configured Git API token to a user-controlled `serverURL` when the user omits the `token` parameter. A tenant with TaskRun or PipelineRun create permission can exfiltrate the shared API token (GitHub PAT, GitLab token, etc.) by pointing `serverURL` to an attacker-controlled endpoint. ### Details The git resolver's `ResolveAPIGit()` function in `pkg/resolution/resolver/git/resolver.go` constructs an SCM client using the user-supplied `serverURL` and a token obtained via `getAPIToken()`. When the user provides `server

O3 Security · Impact-Aware SCA

Is GHSA-wjxp-xrpv-xpff in your dependencies?

O3 detects GHSA-wjxp-xrpv-xpff across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-wjxp-xrpv-xpff

Real-World Exposure

Description

Summary

Details

Impact

Patches

Workarounds

Affected Versions

Acknowledgments

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-wjxp-xrpv-xpff in your dependencies?