CVE-2026-50268: CWE-256: Plaintext Storage of a Password in SteeltoeOSS Steeltoe.Configuration.Encryption
Steeltoe.Configuration.Encryption versions 4.0.0 through 4.1.0 contain a vulnerability where configuring RSA encryption with the OAEP algorithm does not actually enable OAEP. Instead, due to an incorrect transformation string in the BouncyCastle library, the OAEP setting falls back to using PKCS#1 v1.5 encryption, which is less secure. This issue is fixed in version 4.2.0.
AI Analysis
Technical Summary
The vulnerability in Steeltoe.Configuration.Encryption (CVE-2026-50268) arises from a misconfiguration in the encryption algorithm selection. When users configure the encryption setting `encrypt:rsa:algorithm=OAEP` in versions 4.0.0 through 4.1.0, the intended OAEP encryption is not applied. Instead, the system uses PKCS#1 v1.5 due to an incorrect BouncyCastle transformation string. This weakens the encryption strength compared to OAEP. The issue is resolved in version 4.2.0 where the correct transformation string enables OAEP as expected.
Potential Impact
The impact is limited to the encryption algorithm used by Steeltoe.Configuration.Encryption when OAEP is selected. Instead of the more secure OAEP padding, the system uses PKCS#1 v1.5 padding, which is known to be less secure. This could reduce the cryptographic strength of encrypted data, potentially making it more susceptible to certain cryptographic attacks. The CVSS score of 1.9 and low severity reflect the limited impact and the requirement for local access with high privileges to exploit.
Mitigation Recommendations
Upgrade Steeltoe.Configuration.Encryption to version 4.2.0 or later, where the issue is fixed and OAEP encryption is correctly enabled. There is no official patch link provided, but the vendor has addressed the problem in version 4.2.0. Until upgrading, users should be aware that selecting OAEP does not provide the intended encryption strength.
CVE-2026-50268: CWE-256: Plaintext Storage of a Password in SteeltoeOSS Steeltoe.Configuration.Encryption
Description
Steeltoe.Configuration.Encryption versions 4.0.0 through 4.1.0 contain a vulnerability where configuring RSA encryption with the OAEP algorithm does not actually enable OAEP. Instead, due to an incorrect transformation string in the BouncyCastle library, the OAEP setting falls back to using PKCS#1 v1.5 encryption, which is less secure. This issue is fixed in version 4.2.0.
CVSS v3.1
Score 1.9low
Affected software
pkg:nuget/SteeltoeOSS/steeltoe.configuration.encryptionRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Steeltoe.Configuration.Encryption (CVE-2026-50268) arises from a misconfiguration in the encryption algorithm selection. When users configure the encryption setting `encrypt:rsa:algorithm=OAEP` in versions 4.0.0 through 4.1.0, the intended OAEP encryption is not applied. Instead, the system uses PKCS#1 v1.5 due to an incorrect BouncyCastle transformation string. This weakens the encryption strength compared to OAEP. The issue is resolved in version 4.2.0 where the correct transformation string enables OAEP as expected.
Potential Impact
The impact is limited to the encryption algorithm used by Steeltoe.Configuration.Encryption when OAEP is selected. Instead of the more secure OAEP padding, the system uses PKCS#1 v1.5 padding, which is known to be less secure. This could reduce the cryptographic strength of encrypted data, potentially making it more susceptible to certain cryptographic attacks. The CVSS score of 1.9 and low severity reflect the limited impact and the requirement for local access with high privileges to exploit.
Mitigation Recommendations
Upgrade Steeltoe.Configuration.Encryption to version 4.2.0 or later, where the issue is fixed and OAEP encryption is correctly enabled. There is no official patch link provided, but the vendor has addressed the problem in version 4.2.0. Until upgrading, users should be aware that selecting OAEP does not provide the intended encryption strength.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-04T16:26:05.984Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a33211cf198dc38c11fab43
Added to database: 06/17/2026, 22:35:08 UTC
Last enriched: 07/02/2026, 23:06:51 UTC
Last updated: 07/12/2026, 19:47:36 UTC
Views: 63
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.