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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wjxp-xrpv-xpff can be triaged on real exposure rather than presence alone.

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.

What is the EPSS score for GHSA-wjxp-xrpv-xpff?

GHSA-wjxp-xrpv-xpff has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 34th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-wjxp-xrpv-xpff?

GHSA-wjxp-xrpv-xpff is classified as CWE-201 (CWE-201). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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 September 10, 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 — pipeline

HIGH

GHSA-wjxp-xrpv-xpff is a high-severity (CVSS 7.7) CWE-201 vulnerability in github.com/tektoncd/pipeline. A fix is available for github.com/tektoncd/pipeline — see the affected versions and patch details below.

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

Sep 10, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-wjxp-xrpv-xpff.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs34th percentile — riskier than 34% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-wjxp-xrpv-xpff plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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 get github.com/tektoncd/pipeline@v1.0.2`
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.2.0&&< 1.3.4	1.3.4`go get github.com/tektoncd/pipeline@v1.3.4`
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.4.0&&< 1.6.2	1.6.2`go get github.com/tektoncd/pipeline@v1.6.2`
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.7.0&&< 1.9.3	1.9.3`go get github.com/tektoncd/pipeline@v1.9.3`
🐹Go	`github.com/tektoncd/pipeline`	≥ 1.10.0&&< 1.11.1	1.11.1`go get github.com/tektoncd/pipeline@v1.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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-wjxp-xrpv-xpff can be triaged on real exposure rather than presence alone.

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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This Moderate impact information disclosure flaw affects Tekton Pipelines. A user with permissions to create TaskRun or PipelineRun resources could exfiltrate the system-configured Git API token by directing the serverURL to an attacker-controlled endpoint and omitting the token parameter. This vulnerability doesn't…

Product	Fixed in	Advisory
Red Hat OpenShift Builds 1.7.3	`openshift-builds/openshift-builds-controller-rhel9:1780373846`	RHSA-2026:24359
Red Hat OpenShift Pipelines 1.21	`serve-tkn-cli-1-21-serve-tkn-cli-1.21.1`	RHSA-2026:24484

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 Security finds GHSA-wjxp-xrpv-xpff across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CVSS Score

7.7/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

CWE Classification

CWE-201CWE-201

Weaponization

No known public exploit tooling found.

Timeline

Disclosed

Apr 21, 2026

Last updated

Sep 10, 2026

Identifiers

GHSA-wjxp-xrpv-xpff

GO-2026-5711

References

Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Packagegithub.com

Related vulnerabilities

This CVE is high severity; 3 of 8 other CVEs affecting pipeline are rated as high or higher (top: critical).

CVE-2026-40938CVE-2026-40924CVE-2026-25542CVE-2026-40923CVE-2026-40161CVE-2026-33211CVE-2026-33022CVE-2023-37264

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedSep 10, 2026

GHSA-wjxp-xrpv-xpff — pipeline

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

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

Fixing This On Your OS

Frequently Asked Questions

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