![Streamlabs mobile](https://cdn1.cdnme.se/5447227/9-3/14_64e61dfbddf2b36505b4c7c8.png)
![adobe reader for windows 11 adobe reader for windows 11](https://3.bp.blogspot.com/-vCRQRYEr9h8/UxqxIZQf6FI/AAAAAAAAADo/t3F1X21thGE/s1600/mzl.phuboize.png)
This complements Microsoft's own Control Flow Guard (CFG). This includes compile-time mitigations such as Intel's new Control Flow Enforcement Technology (CET), enabled in Microsoft Edge with update 94 for CPUs that support it. "Alongside PartitionAlloc, we ensured that a suite of additional technical countermeasures, also already used across Microsoft Edge, were compatible with the new PDF stack. Microsoft also details its own contributions to Edge security mitigations. Chrome has its own PDF viewer, so it is very likely not using Adobe Reader or Acrobat (unless you reconfigured it to use the Adobe viewer). "This unique heap implementation provides a rapid understanding of vulnerabilities and a strong layer of protection that the new PDF stack will benefit from," Microsoft says. All of these help mitigate memory flaws like use-after frees, but they also create a performance overhead. This includes using security features developed by Google's Chromium team to mitigate C++-related memory flaws, including the relatively recent add-ons for MiraclePtr and heap memory scanning, as well as PartitionAlloc, Chromium's memory allocator. It says the Microsoft Edge Vulnerability Research team was "heavily involved" in the process of bringing the Acrobat engine into Edge. Microsoft detailed some of the work it's done to secure the browser's PDF stack. Turner claims that "using the free PDF experience with the Adobe engine will not allow Adobe to collect any data from you."
![Streamlabs mobile](https://cdn1.cdnme.se/5447227/9-3/14_64e61dfbddf2b36505b4c7c8.png)