How severe is GHSA-rxrh-4j9h-xgg9?

GHSA-rxrh-4j9h-xgg9 has a CVSS score of 4.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rxrh-4j9h-xgg9?

GHSA-rxrh-4j9h-xgg9 affects the following packages: Steeltoe.Configuration.Abstractions (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-rxrh-4j9h-xgg9?

Update Steeltoe.Configuration.Abstractions to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rxrh-4j9h-xgg9 is resolved across your whole dependency graph.

How do I detect GHSA-rxrh-4j9h-xgg9 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Steeltoe.Configuration.Abstractions. 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-rxrh-4j9h-xgg9 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-rxrh-4j9h-xgg9?

O3 pinpoints whether GHSA-rxrh-4j9h-xgg9 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-rxrh-4j9h-xgg9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rxrh-4j9h-xgg9 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 type of vulnerability is GHSA-rxrh-4j9h-xgg9?

GHSA-rxrh-4j9h-xgg9 is classified as CWE-312 (CWE-312), CWE-732 (CWE-732). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rxrh-4j9h-xgg9 published, and has it been updated?

GHSA-rxrh-4j9h-xgg9 was published on July 2, 2026 and was last updated on July 2, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

GHSA-rxrh-4j9h-xgg9

MEDIUM

Steeltoe: TLS private keys written to /tmp with default permissions, never deleted

Also known asCVE-2026-50267

Published

Jul 2, 2026

Updated

Jul 2, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

.NETSteeltoe.Configuration.Abstractions

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

Description

Summary

When MySQL or PostgreSQL service bindings from VCAP_SERVICES include TLS client credentials, the Connectors library writes those credentials to temporary files in Path.GetTempPath() using File.CreateText. On Linux, File.CreateText creates files with mode 0644 (world-readable) under the process umask, and the files are never deleted. The same key material is protected at mode 0400 in /proc/<pid>/environ.

Impact

Any process co-located in the container that runs as a different UID can read the TLS client private key from /tmp and use it to impersonate the application when connecting to the backing database over mutual TLS.

Affected configuration

Application is deployed on Cloud Foundry or another environment that populates VCAP_SERVICES with a MySQL or PostgreSQL service binding that includes sslKey credentials.
A process running as a different UID shares the container's filesystem.

Mitigations

If an immediate upgrade is not possible, prevent other processes from running in the container under a different UID with access to /tmp.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Steeltoe.Configuration.Abstractions`	≥ 4.0.0&&< 4.2.0	4.2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Steeltoe.Configuration.Abstractions. 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 Steeltoe.Configuration.Abstractions to 4.2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rxrh-4j9h-xgg9 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-rxrh-4j9h-xgg9 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-rxrh-4j9h-xgg9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary When MySQL or PostgreSQL service bindings from `VCAP_SERVICES` include TLS client credentials, the Connectors library writes those credentials to temporary files in `Path.GetTempPath()` using `File.CreateText`. On Linux, `File.CreateText` creates files with mode `0644` (world-readable) under the process umask, and the files are never deleted. The same key material is protected at mode `0400` in `/proc/<pid>/environ`. ### Impact Any process co-located in the container that runs as a different UID can read the TLS client private key from `/tmp` and use it to impersonate the applic

O3 Security · Impact-Aware SCA

Is GHSA-rxrh-4j9h-xgg9 in your dependencies?

O3 detects GHSA-rxrh-4j9h-xgg9 across NuGet 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