{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57951 exists.","fix":"No fix has been published for CVE-2026-57951 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-57951 is a high-severity missing authorization vulnerability in its-a-feature Mythic, published on 29 Jun 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-57951 and fix it if it is affected.\n\nWhat it is: CVE-2026-57951 is a high-severity missing authorization vulnerability in its-a-feature Mythic, published on 29 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-57951 exists.\n\nAffected product: its-a-feature Mythic. 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-57951/ (Markdown: https://insights.sbomify.com/CVE-2026-57951/index.md)","id":"CVE-2026-57951","markdown":"https://insights.sbomify.com/CVE-2026-57951/index.md","name":"CVE-2026-57951","record":{"aliases":["GHSA-9f32-pf5h-p947"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mythic C2 framework","requires_auth":"low_privilege","summary":"Authenticated users can bypass permission filters to read sensitive build step logs from all operations in the Mythic C2 framework.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"mythic","vendor":"its-a-feature"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"Mythic before 3.4.0.60 contains a broken hasura permission filter on the payload_build_step table with an always-satisfied _or condition that bypasses operation-scoped access controls. Authenticated operators and spectators can query payload_build_step to read step_stdout, step_stderr, step_name, and step_description across all operations on the server.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Mythic \u003c 3.4.0.60 - Broken Permission Filter in payload_build_step Table","id":"CVE-2026-57951","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Mythic \u003c 3.4.0.60 - Unauthorized C2 Profile Configuration Access via Unverified Payload UUID","id":"CVE-2026-57952"},"packages":[],"prev":{"headline":"ruoyi-vue-pro - Incorrect Permission Namespace in ErpSaleOrderController","id":"CVE-2026-57950"},"products":["Mythic"],"published":"2026-06-29","related":[{"cvss_score":6,"headline":"Mythic \u003c 3.4.0.60 - Unauthorized C2 Profile Configuration Access via Unverified Payload UUID","id":"CVE-2026-57952","kev_date_added":null,"published":"2026-06-29"},{"cvss_score":5.3,"headline":"Mythic \u003c 3.4.0.60 - Unauthorized Automation Workflow Modification via eventing_import_automatic_webhook Endpoint","id":"CVE-2026-57953","kev_date_added":null,"published":"2026-06-29"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["its-a-feature"]},"summary":"Authenticated users can bypass permission filters to read sensitive build step logs from all operations in the Mythic C2 framework.","url":"https://insights.sbomify.com/CVE-2026-57951/"}