{"answers":{"affected":"2 open source packages ship an affected version, including Steeltoe.Configuration.Encryption.","exploited":"There is no known exploitation of CVE-2026-50268 in the wild and no public exploit code.","fix":"Upgrade Steeltoe.Configuration.Encryption to 4.2.0 or later.","what":"CVE-2026-50268 is a low-severity vulnerability in SteeltoeOSS Steeltoe.Configuration.Encryption, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-50268 and fix it if it is affected.\n\nWhat it is: CVE-2026-50268 is a low-severity vulnerability in SteeltoeOSS Steeltoe.Configuration.Encryption, published on 17 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-50268 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Steeltoe.Configuration.Encryption (NuGet): affected from 4.0.0; fixed in 4.2.0\n- Steeltoe.Configuration.Encryption (NuGet): affected from 4.0.0; fixed in 4.2.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-50268/ (Markdown: https://insights.sbomify.com/CVE-2026-50268/index.md)","id":"CVE-2026-50268","markdown":"https://insights.sbomify.com/CVE-2026-50268/index.md","name":"CVE-2026-50268","record":{"aliases":["GHSA-4j9m-h44m-2hv8"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Steeltoe encryption library","requires_auth":"high_privilege","summary":"Misconfigured OAEP setting silently uses weaker PKCS#1 v1.5 padding, reducing encryption security in Steeltoe applications.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":1.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"},{"id":"CWE-256","name":"Plaintext Storage of a Password"}],"description":"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.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Steeltoe: OAEP setting silently selects PKCS#1 v1.5 padding","id":"CVE-2026-50268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":2,"n_references":2,"next":{"headline":"AIOHTTP: CRLF injection in multipart headers","id":"CVE-2026-50269"},"packages":[{"ecosystem":"NuGet","fixed":["4.2.0"],"introduced":["4.0.0"],"last_affected":[],"package":"Steeltoe.Configuration.Encryption","purl":null,"source":"GHSA-4j9m-h44m-2hv8"},{"ecosystem":"NuGet","fixed":["4.2.0"],"introduced":["4.0.0"],"last_affected":[],"package":"Steeltoe.Configuration.Encryption","purl":"pkg:nuget/Steeltoe.Configuration.Encryption","source":"GHSA-4j9m-h44m-2hv8"}],"prev":{"headline":"Steeltoe: TLS private keys written to /tmp with default permissions, never deleted","id":"CVE-2026-50267"},"products":["Steeltoe.Configuration.Encryption"],"published":"2026-06-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-18","vendors":["SteeltoeOSS"]},"summary":"Misconfigured OAEP setting silently uses weaker PKCS#1 v1.5 padding, reducing encryption security in Steeltoe applications.","url":"https://insights.sbomify.com/CVE-2026-50268/"}