{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42099 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-42099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-42099 is a high-severity vulnerability in Sparx Systems Pro Cloud Server, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42099 and fix it if it is affected.\n\nWhat it is: CVE-2026-42099 is a high-severity vulnerability in Sparx Systems Pro Cloud Server, published on 19 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-42099 in the wild and no public exploit code.\n\nAffected product: Sparx Systems Pro Cloud Server. 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-42099/ (Markdown: https://insights.sbomify.com/CVE-2026-42099/index.md)","id":"CVE-2026-42099","markdown":"https://insights.sbomify.com/CVE-2026-42099/index.md","name":"CVE-2026-42099","record":{"aliases":["GHSA-qff4-m3j5-xcv5"],"analysis":{"component_type":"server_software","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Sparx Pro Cloud Server","requires_auth":"low_privilege","summary":"An attacker with repository access can exploit a race condition to execute arbitrary PHP code on Sparx Pro Cloud Server.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"pro_cloud_server","vendor":"sparxsystems"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Sparx Pro Cloud Server is vulnerable to a Race Condition in the /data_api/dl_internal_artifact.php endpoint. The application downloads the properties of the object pointed by guid parameter and saves loaded content in current location (__DIR__) under the specified name. An attacker with repository access can control both the filename and file contents, allowing the creation of a malicious PHP file in a current directory. Although the file is deleted after processing, a race condition exists: if the response transmission is delayed (e.g., via a large file or slow client connection), the file remains accessible. During this window, the attacker can issue a second request to execute the malicious PHP file, resulting in remote code execution.\n\nThe vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.1 (build 167) and below were tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Race Condition in Sparx Pro Cloud Server","id":"CVE-2026-42099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"DoS in Sparx Pro Cloud Server","id":"CVE-2026-42100"},"packages":[],"prev":{"headline":"Authorization Bypass in Sparx Enterprise Architect","id":"CVE-2026-42098"},"products":["Pro Cloud Server"],"published":"2026-05-19","related":[{"cvss_score":9.5,"headline":"Unauthenticated execution of arbitrary SQL queries in Sparx Pro Cloud Server","id":"CVE-2025-15625","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":9.3,"headline":"Authentication Bypass in Sparx Pro Cloud Server","id":"CVE-2026-42097","kev_date_added":null,"published":"2026-05-19"},{"cvss_score":9.3,"headline":"Sparx Pro Cloud Server reveals sensitive information to an unauthenticated user","id":"CVE-2025-15623","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":9.3,"headline":"Plaintext Storage of a Password in Sparx Pro Cloud Server.","id":"CVE-2025-15624","kev_date_added":null,"published":"2026-04-17"},{"cvss_score":8.7,"headline":"Broken Access Control in Sparx Pro Cloud Server","id":"CVE-2026-42096","kev_date_added":null,"published":"2026-05-19"},{"cvss_score":7.1,"headline":"DoS in Sparx Pro Cloud Server","id":"CVE-2026-42100","kev_date_added":null,"published":"2026-05-19"}],"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":"total"},"state":"PUBLISHED","updated":"2026-05-19","vendors":["Sparx Systems"]},"summary":"An attacker with repository access can exploit a race condition to execute arbitrary PHP code on Sparx Pro Cloud Server.","url":"https://insights.sbomify.com/CVE-2026-42099/"}