{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-59301 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-59301 is a low-severity vulnerability in Spring Cloud Function, published on 27 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-59301 and fix it if it is affected.\n\nWhat it is: CVE-2026-59301 is a low-severity vulnerability in Spring Cloud Function, published on 27 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-59301 in the wild and no public exploit code.\n\nAffected product: Spring Cloud Function. 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-59301/ (Markdown: https://insights.sbomify.com/CVE-2026-59301/index.md)","id":"CVE-2026-59301","markdown":"https://insights.sbomify.com/CVE-2026-59301/index.md","name":"CVE-2026-59301","record":{"aliases":["GHSA-mrhq-pfwx-89gm"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Cloud Function Azure","requires_auth":"high_privilege","summary":"Attackers can access sensitive data logged by Spring Cloud Function Azure, requiring developers to upgrade the library.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_cloud_function","vendor":"vmware"}],"cvss":{"score":3.1,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"Potential for logging sensitive data in Spring Cloud Function Azure.\nSpring Cloud Function 5.0.0 - 5.0.3\nSpring Cloud Function 4.3.0 - 4.3.4\nSpring Cloud Function 4.2.0 - 4.2.7","ecosystems":[],"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":"Potential for logging sensitive data in Spring Cloud Function Azure","id":"CVE-2026-59301","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Potential for logging sensitive data in Spring Cloud Stream","id":"CVE-2026-59302"},"packages":[],"prev":{"headline":"Potential for logging sensitive data in Spring Cloud Function AWS","id":"CVE-2026-59300"},"products":["Spring Cloud Function"],"published":"2026-08-27","related":[{"cvss_score":7.5,"headline":"Denial of Service in Spring Cloud Function","id":"CVE-2022-22979","kev_date_added":null,"published":"2022-06-21"},{"cvss_score":5.7,"headline":"Self Routing guard bypassed via function composition","id":"CVE-2026-40989","kev_date_added":null,"published":"2026-06-01"},{"cvss_score":5.7,"headline":"Unbounded cache for function definitions","id":"CVE-2026-40990","kev_date_added":null,"published":"2026-06-01"},{"cvss_score":3.1,"headline":"Spring Cloud Function can incorrectly determine if URI is secure","id":"CVE-2026-59297","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":3.1,"headline":"Potential for improper filtering of HTTP headers in Spring Cloud Function","id":"CVE-2026-59298","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":3.1,"headline":"Composition lookup can potentially poison base function in Spring Cloud Function","id":"CVE-2026-59299","kev_date_added":null,"published":"2026-08-27"},{"cvss_score":3.1,"headline":"Potential for logging sensitive data in Spring Cloud Function AWS","id":"CVE-2026-59300","kev_date_added":null,"published":"2026-08-27"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-08-28","vendors":["Spring"]},"summary":"Attackers can access sensitive data logged by Spring Cloud Function Azure, requiring developers to upgrade the library.","url":"https://insights.sbomify.com/CVE-2026-59301/"}