{"id":117881,"date":"2022-07-13T09:00:00","date_gmt":"2022-07-13T16:00:00","guid":{"rendered":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/?p=117881"},"modified":"2025-06-19T23:33:03","modified_gmt":"2025-06-20T06:33:03","slug":"uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/","title":{"rendered":"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Microsoft uncovered a vulnerability in macOS that could allow specially crafted codes to escape the App Sandbox and run unrestricted on the system. We shared these findings with Apple through <a href=\"https:\/\/www.microsoft.com\/en-us\/msrc\/cvd?rtc=1\">Coordinated Vulnerability Disclosure<\/a> (CVD) via <a href=\"https:\/\/www.microsoft.com\/en-us\/msrc\/msvr\">Microsoft Security Vulnerability Research<\/a> (MSVR) in October 2021. A fix for this vulnerability, now identified as <a href=\"https:\/\/cve.mitre.org\/cgi-bin\/cvename.cgi?name=CVE-2022-26706\">CVE-2022-26706<\/a>, was included in the security updates released by Apple on May 16, 2022. Microsoft shares the vulnerability disclosure credit with another researcher, Arsenii Kostromin (0x3c3e), who discovered a similar technique independently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We encourage macOS users to install these security updates as soon as possible. We also want to thank the Apple product security team for their responsiveness in fixing this issue.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The App Sandbox is Apple\u2019s access control technology that application developers must adopt to distribute their apps through the Mac App Store. Essentially, an app\u2019s processes are enforced with customizable rules, such as the ability to read or write specific files. The App Sandbox also restricts the processes\u2019 access to system resources and user data to minimize the impact or damage if the app becomes compromised. However, we found that specially crafted codes could bypass these rules. An attacker could take advantage of this sandbox escape vulnerability to gain elevated privileges on the affected device or execute malicious commands like installing additional payloads.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">We found the vulnerability while researching potential ways to run and detect malicious macros in Microsoft Office on macOS. For backward compatibility, Microsoft Word can read or write files with an <em>\u201c~$\u201d<\/em> prefix. Our findings revealed that it was possible to escape the sandbox by leveraging macOS\u2019s Launch Services to run an <em>open &#8211;stdin<\/em> command on a specially crafted Python file with the said prefix.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our research shows that even the built-in, baseline security features in macOS could still be bypassed, potentially compromising system and user data. Therefore, collaboration between vulnerability researchers, software vendors, and the larger security community remains crucial to helping secure the overall user experience. This includes responsibly disclosing vulnerabilities to vendors.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In addition, insights from this case study not only enhance our protection technologies, such as <a href=\"https:\/\/www.microsoft.com\/security\/business\/threat-protection\/endpoint-defender\">Microsoft Defender for Endpoint<\/a>, but they also help strengthen the security strategies of software vendors and the computing landscape at large. This blog post thus provides details of our research and overviews of similar sandbox escape vulnerabilities reported by other security researchers that helped enrich our analysis.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"how-macos-app-sandbox-works\">How macOS App Sandbox works<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In a nutshell, macOS apps can specify sandbox rules for the operating system to enforce on themselves. The App Sandbox restricts system calls to an allowed subset, and the said system calls can be allowed or disallowed based on files, objects, and arguments. Simply put, the sandbox rules are a defense-in-depth mechanism that dictates the kind of operations an application can or can\u2019t do, regardless of the type of user running it. Examples of such operations include:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li class=\"wp-block-list-item\">the kind of files an application can or can\u2019t read or write;<\/li>\n\n\n\n<li class=\"wp-block-list-item\">whether the application can access specific resources such as the camera or the microphone, and;<\/li>\n\n\n\n<li class=\"wp-block-list-item\">whether the application is allowed to perform inbound or outbound network connections.<\/li>\n<\/ul>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"801\" height=\"301\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig1-sandboxed-app-illustration.png\" alt=\"Diagram comparing how user data and system resources access an app without and with App Sandbox. \n\nWithout App Sandbox, all user data and system resources will have unrestricted access to the app.\n\nWith App Sandbox, only the data and resources confined within the said sandbox will have unrestricted access to the app. All other user data and resources won't have access.\" class=\"wp-image-117884\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig1-sandboxed-app-illustration.png 801w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig1-sandboxed-app-illustration-300x113.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig1-sandboxed-app-illustration-768x289.png 768w\" sizes=\"auto, (max-width: 801px) 100vw, 801px\" \/><figcaption class=\"wp-element-caption\">Figure 1. Illustration of a sandboxed app, from the App Sandbox <a href=\"https:\/\/developer.apple.com\/library\/archive\/documentation\/Security\/Conceptual\/AppSandboxDesignGuide\/AboutAppSandbox\/AboutAppSandbox.html\">documentation<\/a> (photo credit: Apple)<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, the App Sandbox is a useful tool for all macOS developers in providing baseline security for their applications, especially for those that have large attack surfaces and run user-provided code. One example of these applications is Microsoft Office.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"sandboxing-microsoft-office-in-macos\">Sandboxing Microsoft Office in macOS<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Attackers have targeted Microsoft Office in their attempts to gain a foothold on devices and networks. One of their techniques is abusing Office macros, which they use in social engineering attacks to trick users into downloading malware and other payloads.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">On Windows systems, <a href=\"https:\/\/docs.microsoft.com\/microsoft-365\/security\/office-365-security\/install-app-guard?view=o365-worldwide\">Microsoft Defender Application Guard for Office<\/a> helps secure Microsoft Office against such macro abuse by isolating the host environment using Hyper-V. With this feature enabled, an attacker must first be equipped with a <a href=\"https:\/\/www.microsoft.com\/msrc\/bounty-hyper-v\">Hyper-V guest-to-host vulnerability<\/a> to affect the host system\u2014a very high bar compared to simply running a macro. Without a similar isolation technology and default setting on macOS, Office must rely on the operating system\u2019s existing mitigation strategies. Currently, the most promising technology is the macOS App Sandbox.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Viewing the Microsoft sandbox rules is quite straightforward with the <em>codesign<\/em> utility. Figure 2 below shows the truncated sandbox rules for Microsoft Word:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"784\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig2-ms-word-sandbox-rules.png\" alt=\"Partial screenshot of a command line interface showing different keys and values related to the App Sandbox rules for Microsoft Word in macOS.\" class=\"wp-image-117887\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig2-ms-word-sandbox-rules.png 800w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig2-ms-word-sandbox-rules-300x294.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig2-ms-word-sandbox-rules-768x753.png 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><figcaption class=\"wp-element-caption\">Figure 2. Viewing the Microsoft Word sandbox rules with the codesign utility<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-size: revert; color: initial;\">One of the rules dictates the kind of files the application is allowed to read or write. As seen in the screenshot of the syntax below, Word is allowed to read or write files with filenames that start with the \u201c~$\u201d prefix. The reason for this rule is rooted in the way Office works internally and remains intact for backward compatibility.<\/span><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"65\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig3-ms-word-file-read-write-sandbox-rule.png\" alt=\"Partial screenshot of a command line interface showing the read\/write App Sandbox rule for Microsoft Word in macOS.\" class=\"wp-image-117890\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig3-ms-word-file-read-write-sandbox-rule.png 800w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig3-ms-word-file-read-write-sandbox-rule-300x24.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig3-ms-word-file-read-write-sandbox-rule-768x62.png 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><figcaption class=\"wp-element-caption\">Figure 3. File read and write sandbox rule for Microsoft Word<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><span style=\"font-size: revert; color: initial;\">Despite the security restrictions imposed by the App Sandbox\u2019s rules on applications, it\u2019s possible for attackers to bypass the said rules and let malicious codes \u201cescape\u201d the sandbox and execute arbitrary commands on an affected device. These codes could be hidden in a specially crafted Word macro, which, as mentioned earlier, is one of the attackers\u2019 preferred entry points.<\/span><\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"previously-reported-office-specific-sandbox-escape-vulnerability\">Previously reported Office-specific sandbox escape vulnerability<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For example, in 2018, <a href=\"https:\/\/www.mdsec.co.uk\/2018\/08\/escaping-the-sandbox-microsoft-office-on-macos\/\">MDSec reported<\/a> a vulnerability in Microsoft Office on macOS that could allow an attacker to bypass the App Sandbox. As explained in their blog post, MDSec\u2019s proof-of-concept (POC) exploit took advantage of the fact that Word could drop files with arbitrary contents to arbitrary directories (even after passing traditional permission checks), as long as these files\u2019 filenames began with a \u201c~$\u201d prefix. This bypass was relatively straightforward: have a specially crafted macro drop a <em>.plist<\/em> file in the user\u2019s <em>LaunchAgents<\/em> directory.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <em>LaunchAgents<\/em> directory is a well-known <a href=\"https:\/\/attack.mitre.org\/techniques\/T1543\/001\/\">persistence mechanism<\/a> in macOS. PLIST files that adhere to a specific structure describe (that is, contain the metadata of) macOS <em>launch agents<\/em> initiated by the <em>launchd<\/em> process when a user signs in. Since these <em>launch agents<\/em> will be the children of <em>launchd<\/em>, they won\u2019t inherit the sandbox rules enforced onto Word, and therefore will be out of the Office sandbox.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Shortly after the above vulnerability was reported, Microsoft deployed a fix that denied file writes to the <em>LaunchAgents<\/em> directory and other folders with similar implications. The said disclosure also prompted us to look into different possible sandbox escapes in Microsoft Word and other applications.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"exploring-launch-services-as-means-of-escaping-the-sandbox\">Exploring Launch Services as means of escaping the sandbox<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In 2020, several <a href=\"https:\/\/desi-jarvis.medium.com\/office365-macos-sandbox-escape-fcce4fa4123c\">blog posts<\/a> described a generic sandbox escape vulnerability in macOS\u2019s <em>\/usr\/bin\/open<\/em> utility, a command commonly used to launch files, folders, and applications just as if a user double-clicked them. While <em>open<\/em> is a handy command, it doesn\u2019t create child processes on its own. Instead, it performs an inter-process communication (IPC) with the macOS Launch Services, whose logic is implemented in the context of the <em>launchd<\/em> process. Launch Services then performs the heavy lifting by resolving the handler and launching the right app. Since <em>launchd<\/em> creates the process, it\u2019s not restricted by the caller\u2019s sandbox, similar to how MDSec\u2019s POC exploit worked in 2018.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, using <em>open<\/em> for sandbox escape purposes isn\u2019t trivial because the destination app must be registered within Launch Services. This means that, for example, one couldn\u2019t run files like <em>osascript<\/em> outside the sandbox using <em>open<\/em>. Our internal offensive security team therefore decided to reassess the <em>open<\/em> utility for sandbox escape purposes and use it in a larger end-to-end attack simulation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our obvious first attempt in creating a POC exploit was to create a macro that launches a shell script with the Terminal app. Surprisingly, the POC didn\u2019t work because files dropped from within the sandboxed Word app were automatically given the extended attribute <em>com.apple.quarantine <\/em>(the same one used by Safari to keep track of internet-downloaded files, as well as by <a href=\"https:\/\/support.apple.com\/en-us\/HT202491\">Gatekeeper<\/a> to block malicious files from executing), and Terminal simply refused to run files with that attribute. We also tried using Python scripts, but the Python app had similar issues running files having the said attribute.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our second attempt was to use application extensibility features. For example, Terminal would run the default macOS shell (<em>zsh<\/em>), which would then run arbitrary commands from files like <em>~\/.zshenv<\/em> before running its own command line. This meant that dropping a <em>.zshenv<\/em> file in the user\u2019s home directory and launching the Terminal app would cause the sandbox escape. However, due to Word\u2019s sandbox rules, dropping a <em>.zshenv<\/em> file wasn\u2019t straightforward, as the rules only allowed an application to write to files that begin with the \u201c~$\u201d prefix.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, there is an interesting way of writing such a file indirectly. macOS was shipped with an application called Archive Utility responsible of extracting archive files (such as ZIP files). Such archives were extracted without any user interaction, and the files inside an archive were extracted in the same directory as the archive itself. Therefore, our second POC worked as follows:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li class=\"wp-block-list-item\">Prepare the payload by creating a <em>.zshenv<\/em> file with arbitrary commands and placing it in a ZIPfile. Encode the ZIPfile contents in a Word macro and drop those contents into a file \u201c~$exploit.zip\u201d in the user\u2019s home directory.<\/li>\n\n\n\n<li class=\"wp-block-list-item\">Launch Archive Utility with the <em>open<\/em> command on the \u201c~$exploit.zip\u201d file. Archive Utility ran outside the sandbox (since it\u2019s the child process of <em>\/usr\/bin\/open<\/em>) and was therefore permitted to create files with arbitrary names. By default, Archive Utility extracted the files next to the archive itself\u2014in our case, the user\u2019s home directory. Therefore, this step successfully created a <em>.zshenv<\/em> file with arbitrary contents in the user\u2019s home directory.<\/li>\n\n\n\n<li class=\"wp-block-list-item\">Launch the Terminal app with the <em>open<\/em> command. Since Terminal hosted <em>zsh<\/em> and <em>zsh<\/em> ran commands from the <em>.zshenv<\/em> file, the said file could escape the Word sandbox successfully.<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"801\" height=\"498\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig4-word-macro-with-sandbox-escape-62cd23a5c7bdd.png\" alt=\"Screenshot of a command line interface showing proof-of-concept exploit code.\" class=\"wp-image-117896\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig4-word-macro-with-sandbox-escape-62cd23a5c7bdd.png 801w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig4-word-macro-with-sandbox-escape-62cd23a5c7bdd-300x187.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig4-word-macro-with-sandbox-escape-62cd23a5c7bdd-768x477.png 768w\" sizes=\"auto, (max-width: 801px) 100vw, 801px\" \/><figcaption class=\"wp-element-caption\">Figure 4. Preparing a Word macro with our sandbox escape for an internal Red Team operation<\/figcaption><\/figure>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"perception-point-s-cve-2021-30864\">Perception Point\u2019s CVE-2021-30864<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">In October 2021, Perception Point published a <a href=\"https:\/\/perception-point.io\/a-technical-analysis-of-cve-2021-30864-bypassing-app-sandbox-restrictions\/\">blog post<\/a> that discussed a similar finding (and more elegant, in our opinion). In the said post, Perception Point released details about their sandbox escape (now identified as <a href=\"https:\/\/www.cve.org\/CVERecord?id=CVE-2021-30864\">CVE-2021-30864<\/a>), which used the following facts:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li class=\"wp-block-list-item\">Every sandboxed process had its own <em>container directory<\/em> that\u2019s used as a \u201cscratch space.\u201d The sandboxed process could write arbitrary files, including arbitrary filenames, to that directory unrestricted.<\/li>\n\n\n\n<li class=\"wp-block-list-item\">The <em>open<\/em> command had an interesting <em>&#8211;env<\/em> option that could set or override arbitrary environment variables for the launched app.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Therefore, Perception Point\u2019s POC exploit was cleverly simple:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li class=\"wp-block-list-item\">Drop a <em>.zshenv<\/em> file in the container directory. This was allowed because sandbox rules weren\u2019t enforced on that directory.<\/li>\n\n\n\n<li class=\"wp-block-list-item\">Launch Terminal with the <em>open<\/em> command but use the <em>&#8211;env<\/em> option to override the <em>HOME<\/em> environment variable to point to the container directory. This made <em>zsh<\/em> consider the user\u2019s home directory to be the container directory, and run commands from the planted <em>.zshenv<\/em> file.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Apple has since patched the vulnerability Perception Point reported in the latest version of macOS, Monterey. While we could still create the \u201c~$exploit.zip\u201d file in the user\u2019s home directory, using <em>open<\/em> to launch the <em>Archive Utility<\/em> on the ZIP file now resulted in it being extracted to the Downloads folder. While this is an interesting behavior, we could no longer use it for sandbox escape purposes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"final-exploit-attempt-revisiting-the-open-command\">Final exploit attempt: Revisiting the \u2018open\u2019 command<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">After discovering that Apple has fixed both variants that abuse .zshenv, , we decided to examine all the command line options of the <em>open<\/em> command. Soon after, we came across the following:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"796\" height=\"86\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig5-stdin-option-in-open-utlility.png\" alt=\"Screenshot of a command line interface with the following text:\n\n--stdin PATH\n       Launches the application with stdin connected to PATH.\" class=\"wp-image-117899\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig5-stdin-option-in-open-utlility.png 796w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig5-stdin-option-in-open-utlility-300x32.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig5-stdin-option-in-open-utlility-768x83.png 768w\" sizes=\"auto, (max-width: 796px) 100vw, 796px\" \/><figcaption class=\"wp-element-caption\">Figure 5. The <em>&#8211;stdin <\/em>option in the open utility as presented by its manual entry<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">As mentioned earlier, we couldn\u2019t run Python with a dropped <em>.py<\/em> file since Python refuses to run files with the \u201c<em>com.apple.quarantine<\/em>\u201d extended attribute. We also considered abusing the <em>PYTHONSTARTUP<\/em> environment variable, but Apple\u2019s fix to CVE-2021-30864 apparently prevented that option, too. However, <em>&#8211;stdin<\/em> bypassed the \u201c<em>com.apple.quarantine<\/em>\u201d extended attribute restriction, as there was no way for Python to know that the contents from its standard input originated from a quarantined file.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Our POC exploit thus became simply as follows:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li class=\"wp-block-list-item\">Drop a \u201c~$exploit.py\u201d file with arbitrary Python commands.<\/li>\n\n\n\n<li class=\"wp-block-list-item\">Run <em>open &#8211;stdin=\u2019~$exploit.py\u2019 -a Python<\/em>, which runs the Python app with our dropped file serving as its standard input. Python happily runs our code, and since it\u2019s a child process of <em>launchd<\/em>, it isn\u2019t bound to Word\u2019s sandbox rules.<\/li>\n<\/ol>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"393\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig6-sample-minimal-poc-exploit.png\" alt=\"Screenshot of a proof-of-concept exploit code.\" class=\"wp-image-117902\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig6-sample-minimal-poc-exploit.png 800w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig6-sample-minimal-poc-exploit-300x147.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig6-sample-minimal-poc-exploit-768x377.png 768w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><figcaption class=\"wp-element-caption\">Figure 6. Sample minimal POC exploit code<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">We also came up with a version that\u2019s short enough to be a Twitter post:<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"801\" height=\"72\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig7-tweetable-poc-exploit.png\" alt=\"Screenshot of a proof-of-concept exploit code.\" class=\"wp-image-117905\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig7-tweetable-poc-exploit.png 801w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig7-tweetable-poc-exploit-300x27.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig7-tweetable-poc-exploit-768x69.png 768w\" sizes=\"auto, (max-width: 801px) 100vw, 801px\" \/><figcaption class=\"wp-element-caption\">Figure 7. \u201cTweetable\u201d POC exploit<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"detecting-app-sandbox-escapes-with-microsoft-defender-for-endpoint\">Detecting App Sandbox escapes with Microsoft Defender for Endpoint<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Since our initial discovery of leveraging Launch Services in macOS for generic sandbox escapes, we have been using our POC exploits in Red Team operations to emulate end-to-end attacks against <a href=\"https:\/\/www.microsoft.com\/security\/business\/threat-protection\/endpoint-defender\">Microsoft Defender for Endpoint<\/a>, improve its capabilities, and challenge our detections. Shortly after our Red Team used our first POC exploit, our Blue Team members used it to train artificial intelligence (AI) models to detect our exploit not only in Microsoft Office but also on any app used for a similar Launch Services-based sandbox escape.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">After we learned of Perception Point\u2019s technique and created our own new exploit technique (the Python POC), our Red Team saw another opportunity to fully test our own detection durability. Indeed, the same set of detection rules that handled our first sandbox escape vulnerability still turned out to be durable\u2014even before the vulnerability related to our second POC exploit was patched.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"800\" height=\"515\" src=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig8-microsoft-defender-endpoint-detecting-sandbox-escape.png\" alt=\"Partial screenshot of Microsoft Defender for Endpoint detecting an Office sandbox escape vulnerability. \n\nThe left panel shows the Alert Story with timestamps. The right panel shows the Alert details, including category, MITRE ATT&amp;CK techniques, detection source, service source, detection status, and other information.\" class=\"wp-image-117908\" srcset=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig8-microsoft-defender-endpoint-detecting-sandbox-escape.png 800w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig8-microsoft-defender-endpoint-detecting-sandbox-escape-300x193.png 300w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig8-microsoft-defender-endpoint-detecting-sandbox-escape-768x494.png 768w, https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/fig8-microsoft-defender-endpoint-detecting-sandbox-escape-200x130.png 200w\" sizes=\"auto, (max-width: 800px) 100vw, 800px\" \/><figcaption class=\"wp-element-caption\">Figure 8. Microsoft Defender for Endpoint detecting Office sandbox escape<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For Defender for Endpoint customers, such detection durability feeds into the product\u2019s <a href=\"https:\/\/docs.microsoft.com\/microsoft-365\/security\/defender-endpoint\/next-gen-threat-and-vuln-mgt?view=o365-worldwide\">threat and vulnerability management<\/a> capabilities, which allows them to quickly discover, prioritize, and remediate misconfigurations and vulnerabilities\u2014including those affecting non-Windows devices\u2014through a unified security console.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"https:\/\/www.microsoft.com\/microsoft-365\/security\/endpoint-defender\">Learn how Microsoft Defender for Endpoint delivers a complete endpoint security solution across all platforms.<\/a><\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><em><strong>Jonathan Bar Or<br><\/strong>Microsoft 365 Defender Research Team<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Microsoft uncovered a vulnerability in macOS that could allow specially crafted codes to escape the App Sandbox and run unrestricted on the system. We shared these findings with Apple, and fix for this vulnerability, now identified as CVE-2022-26706, was included in the security updates on May 16, 2022.<\/p>\n","protected":false},"author":150,"featured_media":117917,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"ms_queue_id":[],"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","_alt_title":"","ms-ems-related-posts":[],"footnotes":""},"post_tag":[3898,3785],"threat-intelligence":[3739],"content-type":[3663],"job-role":[],"product":[3690,3694],"topic":[3687],"coauthors":[3380],"class_list":["post-117881","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","tag-elevation-of-privilege","tag-macos","threat-intelligence-vulnerabilities-and-exploits","content-type-research","product-microsoft-defender","product-microsoft-defender-for-endpoint","topic-threat-intelligence","review-flag-1694638265-576","review-flag-1694638271-781","review-flag-1-1694638265-354","review-flag-2-1694638266-864","review-flag-3-1694638266-241","review-flag-4-1694638266-512","review-flag-5-1694638266-171","review-flag-6-1694638266-691","review-flag-7-1694638266-851","review-flag-8-1694638266-352","review-flag-artif-1694638272-22","review-flag-new-1694638263-340"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706 | Microsoft Security Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706 | Microsoft Security Blog\" \/>\n<meta property=\"og:description\" content=\"Microsoft uncovered a vulnerability in macOS that could allow specially crafted codes to escape the App Sandbox and run unrestricted on the system. We shared these findings with Apple, and fix for this vulnerability, now identified as CVE-2022-26706, was included in the security updates on May 16, 2022.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/\" \/>\n<meta property=\"og:site_name\" content=\"Microsoft Security Blog\" \/>\n<meta property=\"article:published_time\" content=\"2022-07-13T16:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-06-20T06:33:03+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t<meta property=\"og:image:height\" content=\"600\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Microsoft Threat Intelligence\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Microsoft Threat Intelligence\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"12 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/\"},\"author\":[{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/author\/microsoft-security-threat-intelligence\/\",\"@type\":\"Person\",\"@name\":\"Microsoft Threat Intelligence\"}],\"headline\":\"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706\",\"datePublished\":\"2022-07-13T16:00:00+00:00\",\"dateModified\":\"2025-06-20T06:33:03+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/\"},\"wordCount\":2350,\"publisher\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg\",\"keywords\":[\"Elevation of privilege\",\"macOS\"],\"articleSection\":[\"Cybersecurity\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/\",\"name\":\"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706 | Microsoft Security Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg\",\"datePublished\":\"2022-07-13T16:00:00+00:00\",\"dateModified\":\"2025-06-20T06:33:03+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg\",\"contentUrl\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg\",\"width\":1200,\"height\":600,\"caption\":\"Black female developer coding on a MacBook Pro in the office, using Visual Studio.\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#website\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/\",\"name\":\"Microsoft Security Blog\",\"description\":\"Expert coverage of cybersecurity topics\",\"publisher\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#organization\",\"name\":\"Microsoft Security Blog\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2018\/08\/cropped-cropped-microsoft_logo_element.png\",\"contentUrl\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2018\/08\/cropped-cropped-microsoft_logo_element.png\",\"width\":512,\"height\":512,\"caption\":\"Microsoft Security Blog\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#\/schema\/person\/a303ddd903ee1f6bdb466c5613e13076\",\"name\":\"Paul Oliveria\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/secure.gravatar.com\/avatar\/13723d0cfef3eb38a618e30474c6973cc20e266c8cac695a2f692654c26036e0?s=96&d=microsoft&r=g44680d3eed0ec5805eb065531f84c245\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/13723d0cfef3eb38a618e30474c6973cc20e266c8cac695a2f692654c26036e0?s=96&d=microsoft&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/13723d0cfef3eb38a618e30474c6973cc20e266c8cac695a2f692654c26036e0?s=96&d=microsoft&r=g\",\"caption\":\"Paul Oliveria\"},\"url\":\"https:\/\/www.microsoft.com\/en-us\/security\/blog\/author\/v-poliveria\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706 | Microsoft Security Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/","og_locale":"en_US","og_type":"article","og_title":"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706 | Microsoft Security Blog","og_description":"Microsoft uncovered a vulnerability in macOS that could allow specially crafted codes to escape the App Sandbox and run unrestricted on the system. We shared these findings with Apple, and fix for this vulnerability, now identified as CVE-2022-26706, was included in the security updates on May 16, 2022.","og_url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/","og_site_name":"Microsoft Security Blog","article_published_time":"2022-07-13T16:00:00+00:00","article_modified_time":"2025-06-20T06:33:03+00:00","og_image":[{"width":1200,"height":600,"url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg","type":"image\/jpeg"}],"author":"Microsoft Threat Intelligence","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Microsoft Threat Intelligence","Est. reading time":"12 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#article","isPartOf":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/"},"author":[{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/author\/microsoft-security-threat-intelligence\/","@type":"Person","@name":"Microsoft Threat Intelligence"}],"headline":"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706","datePublished":"2022-07-13T16:00:00+00:00","dateModified":"2025-06-20T06:33:03+00:00","mainEntityOfPage":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/"},"wordCount":2350,"publisher":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#organization"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage"},"thumbnailUrl":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg","keywords":["Elevation of privilege","macOS"],"articleSection":["Cybersecurity"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/","url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/","name":"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706 | Microsoft Security Blog","isPartOf":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage"},"thumbnailUrl":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg","datePublished":"2022-07-13T16:00:00+00:00","dateModified":"2025-06-20T06:33:03+00:00","breadcrumb":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#primaryimage","url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg","contentUrl":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2022\/07\/macos-sandbox-escape-featured-image.jpg","width":1200,"height":600,"caption":"Black female developer coding on a MacBook Pro in the office, using Visual Studio."},{"@type":"BreadcrumbList","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/2022\/07\/13\/uncovering-a-macos-app-sandbox-escape-vulnerability-a-deep-dive-into-cve-2022-26706\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/"},{"@type":"ListItem","position":2,"name":"Uncovering a macOS App Sandbox escape vulnerability: A deep dive into CVE-2022-26706"}]},{"@type":"WebSite","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#website","url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/","name":"Microsoft Security Blog","description":"Expert coverage of cybersecurity topics","publisher":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#organization","name":"Microsoft Security Blog","url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2018\/08\/cropped-cropped-microsoft_logo_element.png","contentUrl":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-content\/uploads\/2018\/08\/cropped-cropped-microsoft_logo_element.png","width":512,"height":512,"caption":"Microsoft Security Blog"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/#\/schema\/person\/a303ddd903ee1f6bdb466c5613e13076","name":"Paul Oliveria","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/13723d0cfef3eb38a618e30474c6973cc20e266c8cac695a2f692654c26036e0?s=96&d=microsoft&r=g44680d3eed0ec5805eb065531f84c245","url":"https:\/\/secure.gravatar.com\/avatar\/13723d0cfef3eb38a618e30474c6973cc20e266c8cac695a2f692654c26036e0?s=96&d=microsoft&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/13723d0cfef3eb38a618e30474c6973cc20e266c8cac695a2f692654c26036e0?s=96&d=microsoft&r=g","caption":"Paul Oliveria"},"url":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/author\/v-poliveria\/"}]}},"bloginabox_animated_featured_image":null,"bloginabox_display_generated_audio":false,"distributor_meta":false,"distributor_terms":false,"distributor_media":false,"distributor_original_site_name":"Microsoft Security Blog","distributor_original_site_url":"https:\/\/www.microsoft.com\/en-us\/security\/blog","push-errors":false,"_links":{"self":[{"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/posts\/117881","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/users\/150"}],"replies":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/comments?post=117881"}],"version-history":[{"count":1,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/posts\/117881\/revisions"}],"predecessor-version":[{"id":139689,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/posts\/117881\/revisions\/139689"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/media\/117917"}],"wp:attachment":[{"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/media?parent=117881"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/post_tag?post=117881"},{"taxonomy":"threat-intelligence","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/threat-intelligence?post=117881"},{"taxonomy":"content-type","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/content-type?post=117881"},{"taxonomy":"job-role","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/job-role?post=117881"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/product?post=117881"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/topic?post=117881"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/security\/blog\/wp-json\/wp\/v2\/coauthors?post=117881"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}