{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-115417 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-115417 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-115417 is a high-severity vulnerability in aws-c-mqtt, published on 22 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-115417 and fix it if it is affected.\n\nWhat it is: CVE-2026-115417 is a high-severity vulnerability in aws-c-mqtt, published on 22 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-115417 in the wild and no public exploit code.\n\nAffected product: aws-c-mqtt. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-115417/ (Markdown: https://insights.sbomify.com/CVE-2026-115417/index.md)","id":"CVE-2026-115417","markdown":"https://insights.sbomify.com/CVE-2026-115417/index.md","name":"CVE-2026-115417","record":{"aliases":["GHSA-g3x5-86mr-65p5"],"analysis":null,"analysis_generated_by":null,"assigner":"AMZN","cpe":[],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-789","name":"Memory Allocation with Excessive Size Value"}],"description":"Memory allocation with excessive size value in the MQTT 3.1.1 compatibility adapter in AWS aws-c-mqtt before 0.16.2 might allow a remote actor to cause a denial of service of the client application.\n\nTo remediate this issue, users should upgrade to aws-c-mqtt 0.16.2 or later, or to an AWS Common Runtime or AWS IoT Device SDK release that bundles it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Memory allocation with excessive size value in the MQTT 3.1.1 compatibility adapter in aws-c-mqtt","id":"CVE-2026-115417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"SQL injection in the database-query custom resource handlers in the Amazon Web Services (AWS) Cloud Development Kit (CDK) @aws-cdk/aws-redsh","id":"CVE-2026-115418"},"packages":[],"prev":{"headline":"Incorrect authorization checks in Amazon Athena engine version 3 query processing","id":"CVE-2026-115416"},"products":["aws-c-mqtt"],"published":"2026-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-29","vendors":["AWS"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-115417/"}