How severe is GHSA-67x4-qr35-qvrm?

GHSA-67x4-qr35-qvrm has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-67x4-qr35-qvrm?

GHSA-67x4-qr35-qvrm affects the following packages: github.com/flyteorg/flyteadmin (Go). Ecosystems affected: Go.

How do I fix GHSA-67x4-qr35-qvrm?

Update github.com/flyteorg/flyteadmin to 1.1.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67x4-qr35-qvrm is resolved across your whole dependency graph.

How do I detect GHSA-67x4-qr35-qvrm in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/flyteorg/flyteadmin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-67x4-qr35-qvrm if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-67x4-qr35-qvrm actively exploited in the wild?

No public exploit code has been indexed for GHSA-67x4-qr35-qvrm 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-67x4-qr35-qvrm?

GHSA-67x4-qr35-qvrm has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 61th 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-67x4-qr35-qvrm?

GHSA-67x4-qr35-qvrm is classified as Hard-coded Credentials (CWE-798). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-67x4-qr35-qvrm published, and has it been updated?

GHSA-67x4-qr35-qvrm was published on October 5, 2022 and was last updated on May 20, 2024. 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

FlyteAdmin's Default OAuth Authorization Server secret must be rotatedGHSA-67x4-qr35-qvrm

HIGHFix: flyteorg/flyteadmin#478

GHSA-67x4-qr35-qvrm is a high-severity (CVSS 7.5) Hard-coded Credentials vulnerability in github.com/flyteorg/flyteadmin. A fix is available for github.com/flyteorg/flyteadmin — see the affected versions and patch details below.

Also known asCVE-2022-39273GO-2022-1043

Published

Oct 5, 2022

Updated

May 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 11, 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-67x4-qr35-qvrm.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs61th percentile — riskier than 61% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/flyteorg/flyteadmin

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

Impact

Users who enable the default Flyte’s authorization server without changing the default clientid hashes will be exposed to the public internet.

In an effort to make enabling authentication easier for Flyte administrators, the default configuration for Flyte Admin allows access for Flyte Propeller even after turning on authentication via a hardcoded hashed password. This password is also set on the default Flyte Propeller configmap in the various Flyte Helm charts. Users who enable auth but do not override this setting in Flyte Admin’s configuration may unknowingly allow public traffic in by way of this default password with attackers effectively impersonating propeller. This only applies to users who have not specified the ExternalAuthorizationServer setting. Using an external auth server automatically turns off this default configuration is not susceptible to this vulnerability.

Patches

1.1.44

Workarounds

Users should manually set the staticClients in the selfAuthServer section of their configuration if they intend to rely on Admin’s internal auth server.

References

https://github.com/flyteorg/flyteadmin/pull/478 https://docs.flyte.org/en/latest/deployment/cluster_config/auth_setup.html#oauth2-authorization-server

For more information

If you have any questions or comments about this advisory:

Open an issue in Flyte
Email us here

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/flyteorg/flyteadmin`	all versions	1.1.44`go get github.com/flyteorg/flyteadmin@v1.1.44`

Affected Products

1 product · 1 configurations

Application

flyteadminflyte

< 1.1.44

range

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/flyteorg/flyteadmin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/flyteorg/flyteadmin to 1.1.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-67x4-qr35-qvrm is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

### Impact Users who enable the default [Flyte’s authorization server](https://docs.flyte.org/en/latest/deployment/cluster_config/auth_setup.html#oauth2-authorization-server) without changing the default clientid hashes will be exposed to the public internet. In an effort to make enabling authentication easier for Flyte administrators, the default configuration for Flyte Admin allows access for Flyte Propeller even after turning on authentication via a hardcoded hashed password. This password is also set on the default Flyte Propeller configmap in the various Flyte Helm charts. Users who en