{"id":4424,"date":"2026-11-19T06:13:03","date_gmt":"2026-11-19T14:13:03","guid":{"rendered":"https:\/\/cyber.mag212.com\/nginx2root-cve-2026-123007-nginx-http2-rce-patch-guide\/"},"modified":"2026-11-19T06:23:53","modified_gmt":"2026-11-19T14:23:53","slug":"nginx2root-cve-2026-123007-nginx-http2-rce-patch-guide","status":"publish","type":"post","link":"https:\/\/cyber.mag212.com\/fr\/nginx2root-cve-2026-123007-nginx-http2-rce-patch-guide\/","title":{"rendered":"nginx2root (CVE-2026-123007): How a Ten-Year-Old nginx HTTP\/2 Bug Leads to Pre-Auth RCE, and How to Patch"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\"><em>From the <a href=\"https:\/\/cyber.mag212.com\/a-ten-year-old-counter-mag212-cyber-daily-november-19-2026\/\">MAG212 CYBER Daily, 19 November 2026<\/a>. Every command is copied from official documentation or the cited analysis and was <strong>not tested by MAG212<\/strong>; run it only on systems you are authorised to administer.<\/em><\/p>\n\n\n\n<p class=\"m2-status wp-block-paragraph\"><strong>Status:<\/strong> <strong>Fixed on 18 November 2026<\/strong> in nginx 1.31.9 (mainline) and 1.30.7 (stable), and in NGINX Plus 37.3.0.1 and 37.0.8.1. Remote code execution as the nginx worker user was <strong>demonstrated by Xint, Rapid7 and Wiz<\/strong>, and <strong>Rapid7&#8217;s proof of concept is public<\/strong>. <strong>No exploitation in the wild was reported<\/strong> as of 18 November, and the flaw was not in CISA&#8217;s KEV catalog. Severity: CVSS 4.0 9.2; Ubuntu also lists CVSS 3.1 8.1. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-8\">[8]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What happened<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">On 18 November 2026, the nginx project released versions 1.31.9 and 1.30.7, fixing CVE-2026-123007, a memory-corruption bug in HTTP\/2 flow control. nginx.org rates it &#8220;major&#8221; and says it affects every release from 1.9.5, published in September 2015, to 1.31.8. Xint named it nginx2root. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Several teams found it independently. nginx&#8217;s changelog credits Xint, while Rapid7 (researcher Stephen Fewer) and Wiz each reported it to F5 separately and each built a working exploit. The same releases fix four more memory-safety bugs in nginx worker processes: CVE-2026-123633 (HTTP\/2), CVE-2026-123634 (resolver), CVE-2026-121810 (HTTP\/3) and CVE-2026-113425 (mail proxy). <sup><a href=\"#src-3\">[3]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Who is affected<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>nginx open source<\/strong> 1.9.5 through 1.31.8, with HTTP\/2 enabled through <code>listen ... http2<\/code> or <code>http2 on<\/code>. No login and no third-party module is needed: Wiz says serving ordinary static files is enough. <sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><\/li>\n\n<li><strong>NGINX Plus<\/strong> 37.1.0 to 37.2.0.1 and 37.0.0 to 37.0.7.1. Rapid7 and The Hacker News list no fix for R34 to R36. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><\/li>\n\n<li><strong>Linux distributions:<\/strong> on 18 November Ubuntu listed nginx as vulnerable on every supported release from 16.04 to 26.10. Distribution fixes may be backported without changing the version number nginx reports. <sup><a href=\"#src-8\">[8]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><\/li>\n\n<li><strong>Products that embed nginx<\/strong> (ingress controllers, appliances, gateways) need their own vendor&#8217;s update. CIRCL advises following each vendor&#8217;s advisory. <sup><a href=\"#src-7\">[7]<\/a><\/sup><\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The exploit as demonstrated needs an x86-64 build using glibc on a CPU with AVX-512, because it relies on how glibc&#8217;s fast <code>memcpy<\/code> behaves. No source shows other platforms exploitable for code execution, but they should be treated as at least crashable. <sup><a href=\"#src-4\">[4]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Why this matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">nginx sits in front of a huge share of the internet, often as the first thing an attacker can touch. This bug needs no login and no special module, only HTTP\/2, which most modern sites enable by default. A working proof of concept is public, three separate teams found the bug, and the fix needs a full restart rather than the usual reload. Expect scanning and exploit attempts to follow quickly. <em>(MAG212 analysis)<\/em><\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><a href=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/nginx-19nov-diagram.png\"><img decoding=\"async\" src=\"https:\/\/cyber.mag212.com\/wp-content\/uploads\/2026\/11\/nginx-19nov-diagram.png\" alt=\"A ten-year-old counter, pre-auth RCE. Diagram by MAG212 CYBER.\"\/><\/a><figcaption class=\"wp-element-caption\">Diagram: MAG212 CYBER. Solid red = observed or confirmed; dashed amber = reported or unverified; green = recommended control.<\/figcaption><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\">How the attack works<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">HTTP\/2 lets each side tell the other how much data it may send, using a &#8220;window&#8221; that grows with WINDOW_UPDATE frames and shrinks as DATA is sent. Rapid7 and Xint describe the bug chain like this: <sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>The attacker raises the initial window size and opens streams that have DATA queued for sending.<\/li>\n\n<li>The attacker cancels those streams with RST_STREAM. nginx&#8217;s cleanup routine, <code>ngx_http_v2_filter_cleanup()<\/code>, returns the queued credit to the connection&#8217;s send window without checking the 2^31\u22121 maximum.<\/li>\n\n<li>A later WINDOW_UPDATE check in <code>ngx_http_v2_state_window_update()<\/code> subtracts in a way that underflows, so the unsigned counter wraps to a huge value. The HTTP\/2 specification says this should close the connection; nginx keeps it open.<\/li>\n\n<li>When sending, the huge window turns into a negative length, and <code>ngx_ssl_send_chain()<\/code> copies far past the end of its buffer.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Rapid7&#8217;s proof of concept uses that out-of-bounds copy twice: first to leak heap and glibc addresses, which defeats address-space layout randomisation (ASLR), then to overwrite a request-pool cleanup pointer so that nginx calls <code>system()<\/code> with an attacker-chosen command. The command runs as the nginx worker user, not root. <sup><a href=\"#src-4\">[4]<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Root access needs a second, separate bug. Xint chained a Linux kernel SCTP flaw that has no CVE yet and says it escaped a Docker container to host root in its tests. CIRCL&#8217;s guidance: a vulnerable nginx does not by itself mean host root. <sup><a href=\"#src-6\">[6]<\/a><\/sup><sup><a href=\"#src-7\">[7]<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The attack is heavy. Rapid7&#8217;s demonstration sent about 128 GB of HTTP\/2 traffic in about two and a half minutes. That is about 17 minutes at 1 Gbit\/s; below roughly 300 Mbit\/s, nginx&#8217;s default one-hour connection limit gets in the way. A CDN or load balancer that terminates HTTP\/2 in front of nginx may blunt the attack, so test the origin server directly. <sup><a href=\"#src-4\">[4]<\/a><\/sup><sup><a href=\"#src-5\">[5]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Fixed versions<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Product<\/th><th>Vulnerable<\/th><th>Fixed<\/th><\/tr><\/thead><tbody><tr><td>nginx open source (mainline)<\/td><td>1.31.0\u20131.31.8<\/td><td>1.31.9<\/td><\/tr><tr><td>nginx open source (stable)<\/td><td>1.9.5\u20131.30.6<\/td><td>1.30.7<\/td><\/tr><tr><td>NGINX Plus<\/td><td>37.1.0\u201337.2.0.1<\/td><td>37.3.0.1<\/td><\/tr><tr><td>NGINX Plus<\/td><td>37.0.0\u201337.0.7.1<\/td><td>37.0.8.1<\/td><\/tr><tr><td>NGINX Plus<\/td><td>R34\u2013R36<\/td><td>none listed<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Source: Rapid7 and The Hacker News, matching nginx.org. F5&#8217;s own advisory, K000163926, did not load for us; confirm on F5&#8217;s site before deploying. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><sup><a href=\"#src-4\">[4]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to check your servers<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">These read-only commands are taken from CIRCL&#8217;s TR-105 guidance and were <strong>not tested by MAG212<\/strong>. Run them only on systems you administer. <sup><a href=\"#src-7\">[7]<\/a><\/sup><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the version and whether HTTP\/2 is turned on in the configuration nginx will load:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>nginx -v 2&gt;&amp;1<\/code><\/pre>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo nginx -T 2&gt;&amp;1 | sed &#x27;s\/#.*\/\/&#x27; | grep -nE &#x27;listen.*http2|http2 +on|listen.*quic&#x27;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Check whether a listener actually negotiates HTTP\/2. Replace example.org with your host, and test the origin directly if a CDN sits in front:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>openssl s_client -connect example.org:443 -servername example.org -alpn h2 &lt;\/dev\/null 2&gt;&amp;1 | grep -E &#x27;ALPN protocol|No ALPN negotiated&#x27;<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\"><code>ALPN protocol: h2<\/code> means HTTP\/2 is live. Do not publish raw <code>nginx -T<\/code> output: it contains your whole configuration, including paths and upstreams. Check distribution packages with <code>dpkg-query -W 'nginx*'<\/code>, <code>rpm -q nginx<\/code> or <code>apk info -v nginx<\/code>, and read the package changelog, because backported fixes keep old version numbers. <sup><a href=\"#src-7\">[7]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to contain and remediate<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Upgrade<\/strong> to nginx 1.31.9 or 1.30.7, NGINX Plus 37.3.0.1 or 37.0.8.1, or your distribution&#8217;s fixed package. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-2\">[2]<\/a><\/sup><\/li>\n\n<li><strong>Restart fully.<\/strong> A reload leaves the old binary running, and old workers keep serving existing connections. Validate first with <code>nginx -t<\/code>, then restart, or do a live binary upgrade. Rebuild and redeploy container images; official Docker images for 1.31.9 and 1.30.7 were available on 18 November. <sup><a href=\"#src-1\">[1]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><sup><a href=\"#src-7\">[7]<\/a><\/sup><\/li>\n\n<li><strong>If you cannot patch yet, turn HTTP\/2 off.<\/strong> On nginx 1.25.1 and later, remove <code>http2<\/code> from <code>listen<\/code> and set <code>http2 off;<\/code> in every server block sharing that listener, IPv6 included. On older versions, change <code>listen 443 ssl http2;<\/code> to <code>listen 443 ssl;<\/code>. This breaks gRPC and other HTTP\/2-only applications, and it only covers CVE-2026-123007 and CVE-2026-123633. <sup><a href=\"#src-5\">[5]<\/a><\/sup><sup><a href=\"#src-7\">[7]<\/a><\/sup><\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">In CIRCL&#8217;s example, the affected server block keeps <code>listen 443 ssl;<\/code> and adds <code>http2 off;<\/code>, with the rest of its configuration unchanged. <sup><a href=\"#src-7\">[7]<\/a><\/sup><\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Cover the other fixed bugs<\/strong> if you cannot upgrade: use fixed upstreams instead of request-derived DNS names (CVE-2026-123634), remove QUIC listeners and Alt-Svc headers (CVE-2026-121810), and firewall the mail proxy (CVE-2026-113425). <sup><a href=\"#src-6\">[6]<\/a><\/sup><sup><a href=\"#src-7\">[7]<\/a><\/sup><\/li>\n\n<li><strong>Reduce the root path.<\/strong> On hosts that do not need SCTP, CIRCL suggests blocking the kernel module with <code>echo 'install sctp \/bin\/false' | sudo tee \/etc\/modprobe.d\/disable-sctp.conf<\/code>. It does not unload a module already loaded or disable SCTP built into the kernel. For containers, assess the host kernel. <sup><a href=\"#src-7\">[7]<\/a><\/sup><\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\">What defenders should look for<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There is no public network signature. CIRCL, Xint and Wiz suggest behaviour-based checks: <sup><a href=\"#src-5\">[5]<\/a><\/sup><sup><a href=\"#src-6\">[6]<\/a><\/sup><sup><a href=\"#src-7\">[7]<\/a><\/sup><\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Worker crashes: <code>sudo grep -Ei 'worker process.*exited|signal 11|segfault' \/var\/log\/nginx\/error.log<\/code> and <code>sudo coredumpctl list nginx<\/code>.<\/li>\n\n<li>Long-lived connections on port 443 with very large inbound traffic but few logged requests. WINDOW_UPDATE and RST_STREAM frames never appear in access logs. <code>sudo ss -tinp state established '( sport = :443 )'<\/code> shows per-connection byte counts.<\/li>\n\n<li>Processes started by nginx workers, for example with auditd rules on <code>execve<\/code> by the worker&#8217;s user ID, and unexpected outbound or DNS activity from the web server.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A clean access log does not prove a server was not attacked. If you find crash bursts or worker child processes from before you patched, preserve the logs and core dumps and investigate the host.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">How to verify recovery<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>The installed package version or changelog shows the fix, and the running nginx was restarted after the upgrade.<\/li>\n\n<li>Where you turned HTTP\/2 off, the ALPN test no longer returns <code>h2<\/code>.<\/li>\n\n<li>Container images in production are rebuilt from fixed base images.<\/li>\n\n<li>NGINX Plus, ingress and appliance vendors have confirmed their fix status in writing.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Prevention and awareness<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Inventory every place nginx runs, including inside products you do not think of as &#8220;nginx&#8221;. Record which listeners speak HTTP\/2 and QUIC. Make full restarts part of your patch procedure for web servers, and alert on worker crashes as a security signal, not only an availability one. ASLR and position-independent builds help, but CIRCL warns not to close a finding just because they are enabled. <sup><a href=\"#src-7\">[7]<\/a><\/sup><\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related on MAG212 CYBER<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><a href=\"https:\/\/cyber.mag212.com\/a-ten-year-old-counter-mag212-cyber-daily-november-19-2026\/\">MAG212 CYBER Daily, 19 November 2026: A ten-year-old counter<\/a> (full issue and PDF)<\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/one-equals-sign-too-many-mag212-cyber-daily-november-18-2026\/\">MAG212 CYBER Daily, 18 November 2026: One equals sign too many<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/keys-outlived-the-job-mag212-cyber-daily-november-17-2026\/\">MAG212 CYBER Daily, 17 November 2026: Keys that outlived the job<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/the-keys-were-already-inside-mag212-cyber-weekly-november-14-2026\/\">MAG212 CYBER Weekly, 14 November 2026<\/a><\/li>\n\n<li><a href=\"https:\/\/cyber.mag212.com\/subscribe-free\/\">Subscribe free to MAG212 CYBER<\/a><\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><span id=\"src-1\">[1]<\/span> The Hacker News, &#8220;<a href=\"https:\/\/thehackernews.com\/2026\/11\/10-year-old-nginx-http2-flaw-lets.html\" rel=\"noopener\" target=\"_blank\">10-Year-Old NGINX HTTP\/2 Flaw Lets Unauthenticated Attackers Execute Code on Servers<\/a>&#8220;, 18 Nov 2026.<\/li>\n\n<li><span id=\"src-2\">[2]<\/span> nginx.org, &#8220;<a href=\"https:\/\/nginx.org\/en\/security_advisories.html\" rel=\"noopener\" target=\"_blank\">nginx security advisories<\/a>&#8220;, 18 Nov 2026.<\/li>\n\n<li><span id=\"src-3\">[3]<\/span> nginx.org, &#8220;<a href=\"https:\/\/nginx.org\/en\/CHANGES\" rel=\"noopener\" target=\"_blank\">Changes with nginx 1.31.9<\/a>&#8220;, 18 Nov 2026.<\/li>\n\n<li><span id=\"src-4\">[4]<\/span> Rapid7 (S. Fewer), &#8220;<a href=\"https:\/\/www.rapid7.com\/blog\/post\/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed\/\" rel=\"noopener\" target=\"_blank\">CVE-2026-123007: Critical NGINX HTTP\/2 integer underflow leads to RCE (fixed)<\/a>&#8220;, 18 Nov 2026.<\/li>\n\n<li><span id=\"src-5\">[5]<\/span> Wiz Research, &#8220;<a href=\"https:\/\/www.wiz.io\/blog\/nginx-http2-rce-vulnerabilities\" rel=\"noopener\" target=\"_blank\">NGINX HTTP\/2 RCE vulnerabilities<\/a>&#8220;, 18 Nov 2026.<\/li>\n\n<li><span id=\"src-6\">[6]<\/span> Xint (Theori), &#8220;<a href=\"https:\/\/xint.io\/blog\/nginx2root-remote-code-execution\" rel=\"noopener\" target=\"_blank\">nginx2root: remote code execution<\/a>&#8220;, 18 Nov 2026.<\/li>\n\n<li><span id=\"src-7\">[7]<\/span> CIRCL, &#8220;<a href=\"https:\/\/www.circl.lu\/pub\/tr-105\/\" rel=\"noopener\" target=\"_blank\">TR-105 NGINX2ROOT (TLP:CLEAR)<\/a>&#8220;, 18 Nov 2026.<\/li>\n\n<li><span id=\"src-8\">[8]<\/span> Ubuntu, &#8220;<a href=\"https:\/\/ubuntu.com\/security\/CVE-2026-123007\" rel=\"noopener\" target=\"_blank\">CVE-2026-123007<\/a>&#8220;, 18 Nov 2026.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\"><em>Written and edited by El Mostafa Ouchen for MAG212 CYBER. Facts checked against the sources above as of 19 November 2026, 6:00 AM PT.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>A flow-control bug present in nginx since 2015 lets an unauthenticated attacker corrupt memory over HTTP\/2 and run code as the worker user. nginx 1.31.9 and 1.30.7 fix it, and a public proof of concept exists. Who is affected, how it works, fixed versions, the HTTP\/2 workaround, checks and detection.<\/p>","protected":false},"author":1,"featured_media":4409,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,15],"tags":[464,466,333,465,472,463,417,473],"class_list":["post-4424","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-critical-cves","category-threat-intelligence","tag-cve-2026-123007","tag-f5","tag-http-2","tag-nginx","tag-nginx-plus","tag-nginx2root","tag-vulnerability-management","tag-web-server-security"],"_links":{"self":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4424","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/comments?post=4424"}],"version-history":[{"count":1,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4424\/revisions"}],"predecessor-version":[{"id":4434,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/posts\/4424\/revisions\/4434"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media\/4409"}],"wp:attachment":[{"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/media?parent=4424"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/categories?post=4424"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/cyber.mag212.com\/fr\/wp-json\/wp\/v2\/tags?post=4424"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}