{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-3236 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-3236 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3236 is a low-severity vulnerability in Octopus Octopus Server, published on 5 Mar 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-3236 and fix it if it is affected.\n\nWhat it is: CVE-2026-3236 is a low-severity vulnerability in Octopus Octopus Server, published on 5 Mar 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-3236 in the wild and no public exploit code.\n\nAffected product: Octopus Octopus 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-3236/ (Markdown: https://insights.sbomify.com/CVE-2026-3236/index.md)","id":"CVE-2026-3236","markdown":"https://insights.sbomify.com/CVE-2026-3236/index.md","name":"CVE-2026-3236","record":{"aliases":["GHSA-mj9m-c5pr-rxw7"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Octopus Server","requires_auth":"low_privilege","summary":"Attackers can create API keys with longer lifetimes than the original token, bypassing intended expiration controls in Octopus Server.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Octopus","cpe":[{"product":"octopus_server","vendor":"octopus"}],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"In affected versions of Octopus Server it was possible to create a new API key from an existing access token resulting in the new API key having a lifetime exceeding the original API key used to mint the access token.","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 Octopus Server","id":"CVE-2026-3236","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"octopus:octopus_server","products":["octopus:octopus_server"],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in Octopus Server","id":"CVE-2026-3237"},"packages":[],"prev":{"headline":"Missing authorization in WP Data Access – App Builder for Tables, Forms, Charts, Maps \u0026 Dashboards","id":"CVE-2026-3235"},"products":["Octopus Server"],"published":"2026-03-05","related":[{"cvss_score":9.8,"headline":"Auth bypass in Octopus Server","id":"CVE-2022-2572","kev_date_added":null,"published":"2022-11-01"},{"cvss_score":9.8,"headline":"Security feature bypass in Octopus Server","id":"CVE-2022-2778","kev_date_added":null,"published":"2022-09-30"},{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2018-11320","kev_date_added":null,"published":"2018-05-21"},{"cvss_score":9.1,"headline":"Auth bypass in Octopus Server","id":"CVE-2022-2782","kev_date_added":null,"published":"2022-10-26"},{"cvss_score":8.8,"headline":"Race condition in Octopus Server","id":"CVE-2024-2975","kev_date_added":null,"published":"2024-04-09"},{"cvss_score":8.8,"headline":"Command injection in Octopus Server","id":"CVE-2022-4009","kev_date_added":null,"published":"2023-03-16"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2018-18850","kev_date_added":null,"published":"2018-10-31"}],"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-03-05","vendors":["Octopus Deploy"]},"summary":"Attackers can create API keys with longer lifetimes than the original token, bypassing intended expiration controls in Octopus Server.","url":"https://insights.sbomify.com/CVE-2026-3236/"}