{"answers":{"affected":"2 open source packages ship an affected version, including Amazon.Extensions.S3.Encryption.","exploited":"There is no known exploitation of CVE-2025-14759 in the wild and no public exploit code.","fix":"Upgrade Amazon.Extensions.S3.Encryption to 3.2.0 or later.","what":"CVE-2025-14759 is a medium-severity vulnerability in AWS S3 Encryption Client for .NET, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14759 and fix it if it is affected.\n\nWhat it is: CVE-2025-14759 is a medium-severity vulnerability in AWS S3 Encryption Client for .NET, published on 17 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-14759 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- Amazon.Extensions.S3.Encryption (NuGet): affected all versions; fixed in 3.2.0\n- Amazon.Extensions.S3.Encryption (NuGet): affected all versions; fixed in 3.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-2025-14759/ (Markdown: https://insights.sbomify.com/CVE-2025-14759/index.md)","id":"CVE-2025-14759","markdown":"https://insights.sbomify.com/CVE-2025-14759/index.md","name":"CVE-2025-14759","record":{"aliases":["GHSA-4v42-65r3-3gjx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"AWS S3 Encryption Client","requires_auth":"low_privilege","summary":"Missing key commitment in AWS S3 Encryption Client for .NET allows attackers with write access to manipulate encrypted data keys, potentially compromising data integrity and confidentiality.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"AMZN","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"Missing cryptographic key commitment in the Amazon S3 Encryption Client for .NET may allow a user with write access to the S3 bucket to introduce a new EDK that decrypts to different plaintext when the encrypted data key is stored in an \"instruction file\" instead of S3's metadata record.\n\nTo mitigate this issue, upgrade Amazon S3 Encryption Client for .NET to version 3.2.0 or later.","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":"Amazon S3 Encryption Client for .NET has a Key Commitment Issue","id":"CVE-2025-14759","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":2,"n_references":3,"next":{"headline":"Weak cryptography in AWS SDK for C++","id":"CVE-2025-14760"},"packages":[{"ecosystem":"NuGet","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"Amazon.Extensions.S3.Encryption","purl":null,"source":"GHSA-4v42-65r3-3gjx"},{"ecosystem":"NuGet","fixed":["3.2.0"],"introduced":["0"],"last_affected":[],"package":"Amazon.Extensions.S3.Encryption","purl":"pkg:nuget/Amazon.Extensions.S3.Encryption","source":"GHSA-4v42-65r3-3gjx"}],"prev":{"headline":"Initialization of a Resource with an Insecure Default in YAOOK","id":"CVE-2025-14758"},"products":["S3 Encryption Client for .NET"],"published":"2025-12-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":"2025-12-17","vendors":["AWS"]},"summary":"Missing key commitment in AWS S3 Encryption Client for .NET allows attackers with write access to manipulate encrypted data keys, potentially compromising data integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2025-14759/"}