{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55181 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55181 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55181 is a medium-severity denial of service vulnerability in Facebook proxygen, published on 2 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-55181 and fix it if it is affected.\n\nWhat it is: CVE-2025-55181 is a medium-severity denial of service vulnerability in Facebook proxygen, published on 2 Dec 2025. 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-2025-55181 in the wild and no public exploit code.\n\nAffected product: Facebook proxygen. 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-55181/ (Markdown: https://insights.sbomify.com/CVE-2025-55181/index.md)","id":"CVE-2025-55181","markdown":"https://insights.sbomify.com/CVE-2025-55181/index.md","name":"CVE-2025-55181","record":{"aliases":["GHSA-886p-82g3-p77g"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Proxygen library","requires_auth":"none","summary":"An attacker can cause a denial of service by sending oversized HTTP bodies, triggering an infinite loop and memory exhaustion in the Proxygen library.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Meta","cpe":[{"product":"proxygen","vendor":"facebook"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-834","name":"Excessive Iteration"}],"description":"Sending an HTTP request/response body with greater than 2^31 bytes triggers an infinite loop in proxygen::coro::HTTPQuicCoroSession which blocks the backing event loop and unconditionally appends data to a std::vector per-loop iteration. This issue leads to unbounded memory growth and eventually causes the process to run out of memory.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Denial of service in proxygen","id":"CVE-2025-55181","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Meta React Server Components Remote Code Execution","id":"CVE-2025-55182"},"packages":[],"prev":{"headline":"Server-side request forgery in WhatsApp Business for iOS","id":"CVE-2025-55179"},"products":["proxygen"],"published":"2025-12-02","related":[{"cvss_score":9.8,"headline":"Use after free in proxygen","id":"CVE-2020-1897","kev_date_added":null,"published":"2020-05-18"},{"cvss_score":9.8,"headline":"Use after free in Proxygen","id":"CVE-2019-11940","kev_date_added":null,"published":"2019-12-04"},{"cvss_score":9.8,"headline":"Memory corruption in Proxygen","id":"CVE-2019-11921","kev_date_added":null,"published":"2019-07-25"},{"cvss_score":7.5,"headline":"Proxygen fails to validate that a secondary auth manager is set before dereferencing it.","id":"CVE-2018-6343","kev_date_added":null,"published":"2018-12-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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-03","vendors":["Facebook"]},"summary":"An attacker can cause a denial of service by sending oversized HTTP bodies, triggering an infinite loop and memory exhaustion in the Proxygen library.","url":"https://insights.sbomify.com/CVE-2025-55181/"}