{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-9247 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-9247 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9247 is a low-severity vulnerability in Devolutions Devolutions Server, published on 22 May 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-9247 and fix it if it is affected.\n\nWhat it is: CVE-2026-9247 is a low-severity vulnerability in Devolutions Devolutions Server, published on 22 May 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-9247 in the wild and no public exploit code.\n\nAffected product: Devolutions Devolutions 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-9247/ (Markdown: https://insights.sbomify.com/CVE-2026-9247/index.md)","id":"CVE-2026-9247","markdown":"https://insights.sbomify.com/CVE-2026-9247/index.md","name":"CVE-2026-9247","record":{"aliases":["GHSA-3g3q-8qfh-j8w8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Devolutions Server","requires_auth":"high_privilege","summary":"Authenticated users can bypass unseal notifications when exporting sealed entries, hiding sensitive access from administrators.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"DEVOLUTIONS","cpe":[{"product":"devolutions_server","vendor":"devolutions"}],"cvss":{"score":2.4,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-778","name":"Insufficient Logging"}],"description":"Insufficient logging in the entry export feature in Devolutions Server allows an authenticated user with export permissions to export a sealed entry without triggering the unseal notification to administrators via a crafted export request.\n\nThis issue affects :\n\n  *  Devolutions Server 2026.1.6.0 through 2026.1.16.0\n  *  Devolutions Server 2025.3.20.0 and earlier","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":"Security feature bypass in Server","id":"CVE-2026-9247","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"devolutions:devolutions_server","products":["devolutions:devolutions_server"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Server","id":"CVE-2026-9248"},"packages":[],"prev":{"headline":"Missing authorization in Server","id":"CVE-2026-9246"},"products":["Server"],"published":"2026-05-22","related":[{"cvss_score":9.8,"headline":"Business logic in Server","id":"CVE-2026-3130","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":9.8,"headline":"Cross-site scripting in Server","id":"CVE-2026-3204","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":9.8,"headline":"Auth bypass in Server","id":"CVE-2026-3224","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":9.8,"headline":"SQL injection in Server","id":"CVE-2026-0610","kev_date_added":null,"published":"2026-01-19"},{"cvss_score":9.8,"headline":"Missing authorization in Server","id":"CVE-2024-2921","kev_date_added":null,"published":"2024-03-26"},{"cvss_score":9.5,"headline":"Hardcoded credentials in Server","id":"CVE-2025-6523","kev_date_added":null,"published":"2025-07-22"},{"cvss_score":9.1,"headline":"Missing authorization in n/a","id":"CVE-2021-23921","kev_date_added":null,"published":"2021-04-01"}],"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-05-22","vendors":["Devolutions"]},"summary":"Authenticated users can bypass unseal notifications when exporting sealed entries, hiding sensitive access from administrators.","url":"https://insights.sbomify.com/CVE-2026-9247/"}