Vulnerability in Steeltoe.Configuration.Encryption (CVE-2026-50268)
Summary
Vulnerability in Steeltoe.Configuration.Encryption (CVE-2026-50268). Risk of unauthorized operations or information disclosure. Exploitable via OAEP. Mitigation: upgrade to 4.2.0 or later.
Original description
The description as published by the source.
Steeltoe is an open source project that provides a collection of libraries that helps users build cloud-native applications. In Steeltoe.Configuration.Encryption 4.0.0 through 4.1.0, configuring encrypt:rsa:algorithm=OAEP does not enable OAEP encryption. Due to an incorrect BouncyCastle transformation string, the OAEP setting selects PKCS#1 v1.5, which is the same algorithm as the DEFAULT setting. Steeltoe.Configuration.Encryption version 4.2.0 patches the issue.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-50268 has been found in Steeltoe.Configuration.Encryption.
Attackers can target a specific entry point like OAEP over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 1.9/10.
What to do: upgrade Steeltoe.Configuration.Encryption to 4.2.0 or later.
If unsure, ask your IT team or search "Steeltoe.Configuration.Encryption CVE-2026-50268" on the vendor's site.
CVE-2026-50268 (Steeltoe.Configuration.Encryption) — CWE-256 / CVSS v3 1.9
Attack vector: local / no user interaction
Attack surface: OAEP / DEFAULT
Patched: 4.2.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-256) exists in Steeltoe.Configuration.Encryption. Attackers reach the vulnerable code path via OAEP.
Check the vendor advisory for the affected versions of Steeltoe.Configuration.Encryption. Attack surface: OAEP / DEFAULT.
Severity: Low (CVSS 1.9/10). Risk of unauthorized operations or information disclosure.
Update to 4.2.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Steeltoe.Configuration.Encryption' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Steeltoe.Configuration.Encryption' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Steeltoe.Configuration.Encryptionを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Steeltoe.Configuration.Encryption to 4.2.0ステージング環境で 4.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- web github.com