{"answers":{"affected":"4 open source packages ship an affected version, including io.awspring.cloud:spring-cloud-aws-sns.","exploited":"There is no known exploitation of CVE-2026-44308 in the wild and no public exploit code.","fix":"Upgrade io.awspring.cloud:spring-cloud-aws-sns to 4.0.2 or later.","what":"CVE-2026-44308 is a medium-severity vulnerability in awspring spring-cloud-aws, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-44308 and fix it if it is affected.\n\nWhat it is: CVE-2026-44308 is a medium-severity vulnerability in awspring spring-cloud-aws, published on 14 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-44308 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- io.awspring.cloud:spring-cloud-aws-sns (Maven): affected from 3.0.0 up to 3.4.2; no fix listed\n- io.awspring.cloud:spring-cloud-aws-sns (Maven): affected from 3.0.0 up to 3.4.2; no fix listed\n- io.awspring.cloud:spring-cloud-aws-sns (Maven): affected from 4.0.0; fixed in 4.0.2\n- io.awspring.cloud:spring-cloud-aws-sns (Maven): affected from 4.0.0; fixed in 4.0.2\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-44308/ (Markdown: https://insights.sbomify.com/CVE-2026-44308/index.md)","id":"CVE-2026-44308","markdown":"https://insights.sbomify.com/CVE-2026-44308/index.md","name":"CVE-2026-44308","record":{"aliases":["GHSA-r4w4-wv68-qv85","ROOT-APP-MAVEN-CVE-2026-44308"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Spring Cloud AWS library","requires_auth":"none","summary":"Attackers can spoof SNS notifications by bypassing signature verification in Spring Cloud AWS applications using HTTP/HTTPS endpoints.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Spring Cloud AWS simplifies using AWS managed services in a Spring and Spring Boot applications. From 3.0.0 to 4.0.1, pplications using Spring Cloud AWS SNS HTTP/HTTPS endpoint support (@NotificationMessageMapping, @NotificationSubscriptionMapping, @NotificationUnsubscribeConfirmationMapping) did not verify the signature of incoming SNS messages. An unauthenticated attacker who knows the endpoint URL could send crafted HTTP POST requests mimicking SNS Notification or SubscriptionConfirmation messages. This vulnerability is fixed in 4.0.2.","ecosystems":["Maven"],"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":"Spring Cloud AWS: Missing SNS message signature verification allows spoofing of HTTP/HTTPS endpoint notifications","id":"CVE-2026-44308","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":4,"n_references":1,"next":{"headline":"gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits","id":"CVE-2026-44309"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["3.0.0"],"last_affected":["3.4.2"],"package":"io.awspring.cloud:spring-cloud-aws-sns","purl":null,"source":"GHSA-r4w4-wv68-qv85"},{"ecosystem":"Maven","fixed":[],"introduced":["3.0.0"],"last_affected":["3.4.2"],"package":"io.awspring.cloud:spring-cloud-aws-sns","purl":"pkg:maven/io.awspring.cloud/spring-cloud-aws-sns","source":"GHSA-r4w4-wv68-qv85"},{"ecosystem":"Maven","fixed":["4.0.2"],"introduced":["4.0.0"],"last_affected":[],"package":"io.awspring.cloud:spring-cloud-aws-sns","purl":null,"source":"GHSA-r4w4-wv68-qv85"},{"ecosystem":"Maven","fixed":["4.0.2"],"introduced":["4.0.0"],"last_affected":[],"package":"io.awspring.cloud:spring-cloud-aws-sns","purl":"pkg:maven/io.awspring.cloud/spring-cloud-aws-sns","source":"GHSA-r4w4-wv68-qv85"}],"prev":{"headline":"Mako: Path traversal via backslash URI on Windows in TemplateLookup","id":"CVE-2026-44307"},"products":["spring-cloud-aws","spring-cloud-aws-sns"],"published":"2026-05-14","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["awspring","io.awspring.cloud"]},"summary":"Attackers can spoof SNS notifications by bypassing signature verification in Spring Cloud AWS applications using HTTP/HTTPS endpoints.","url":"https://insights.sbomify.com/CVE-2026-44308/"}