{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-67844 exists.","fix":"No fix has been published for CVE-2025-67844 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-67844 is a medium-severity missing authorization vulnerability in Mintlify Platform, published on 19 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-67844 and fix it if it is affected.\n\nWhat it is: CVE-2025-67844 is a medium-severity missing authorization vulnerability in Mintlify Platform, published on 19 Dec 2025. 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-2025-67844 exists.\n\nAffected product: Mintlify Platform. 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-2025-67844/ (Markdown: https://insights.sbomify.com/CVE-2025-67844/index.md)","id":"CVE-2025-67844","markdown":"https://insights.sbomify.com/CVE-2025-67844/index.md","name":"CVE-2025-67844","record":{"aliases":["GHSA-m2jw-wc29-6qmv"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mintlify Platform","requires_auth":"low_privilege","summary":"Remote attackers can access sensitive repository metadata by bypassing validation of repository owner and name fields in the GitHub Integration API.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mintlify","vendor":"mintlify"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-425","name":"Direct Request"}],"description":"The GitHub Integration API in Mintlify Platform before 2025-11-15 allows remote attackers to obtain sensitive repository metadata via the repository owner and name fields. It fails to validate that the repository owner and name fields provided during configuration belong to the specific GitHub App Installation ID associated with the user's organization.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Missing authorization in Mintlify Platform","id":"CVE-2025-67844","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in Mintlify Platform","id":"CVE-2025-67845"},"packages":[],"prev":{"headline":"Code injection in Mintlify Platform","id":"CVE-2025-67843"},"products":["Mintlify Platform"],"published":"2025-12-19","related":[{"cvss_score":8.3,"headline":"Code injection in Mintlify Platform","id":"CVE-2025-67843","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":6.4,"headline":"Cross-site scripting in Mintlify Platform","id":"CVE-2025-67842","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":6.4,"headline":"Path traversal in Mintlify Platform","id":"CVE-2025-67845","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":4.9,"headline":"Security feature bypass in Mintlify Platform","id":"CVE-2025-67846","kev_date_added":null,"published":"2025-12-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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-19","vendors":["Mintlify"]},"summary":"Remote attackers can access sensitive repository metadata by bypassing validation of repository owner and name fields in the GitHub Integration API.","url":"https://insights.sbomify.com/CVE-2025-67844/"}