{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-53904 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-53904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-53904 is a medium-severity denial of service vulnerability in MyComplianceOffice MCO, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53904 and fix it if it is affected.\n\nWhat it is: CVE-2026-53904 is a medium-severity denial of service vulnerability in MyComplianceOffice MCO, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53904 in the wild and no public exploit code.\n\nAffected product: MyComplianceOffice MCO. 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-53904/ (Markdown: https://insights.sbomify.com/CVE-2026-53904/index.md)","id":"CVE-2026-53904","markdown":"https://insights.sbomify.com/CVE-2026-53904/index.md","name":"CVE-2026-53904","record":{"aliases":["GHSA-4p9c-w7qw-q5pq"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Compliance management software","requires_auth":"none","summary":"Attackers can lock victims out of MCO accounts by repeatedly triggering password resets, causing account denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"mco","vendor":"mycomplianceoffice"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-640","name":"Weak Password Recovery Mechanism for Forgotten Password"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"MCO is vulnerable to Account Denial of Service due to improper implementation of password reset functionality. Each password reset request invalidates previously set password as well as previously issued temporary passwords, furthermore, password resets are not limited in any way. An attacker who provides victim's email and answer to their security question, can successfully initiate the reset process and continuously invalidate credentials, effectively locking the victim out of their account. Answering security questions has a limited number of tries which lowers the risk of this vulnerability.\n\nBecause vendor contact attempts were unsuccessful, the vulnerability has only been confirmed in version 25.3.3.1 but may also affect other versions.","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":"Account Denial of Service in MCO","id":"CVE-2026-53904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Unauthorized Access to Administrator ACL View in MCO","id":"CVE-2026-53905"},"packages":[],"prev":{"headline":"Insecure Direct Object Reference in MCO","id":"CVE-2026-53903"},"products":["MCO"],"published":"2026-07-01","related":[],"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-07-01","vendors":["MyComplianceOffice"]},"summary":"Attackers can lock victims out of MCO accounts by repeatedly triggering password resets, causing account denial of service.","url":"https://insights.sbomify.com/CVE-2026-53904/"}