{"id":184322,"date":"2026-11-19T03:36:31","date_gmt":"2026-11-19T01:36:31","guid":{"rendered":"https:\/\/prohoster.info\/blog\/news\/nginx2root-uyazvimosti-v-nginx-pozvolyayushhie-vypolnit-kod-pri-ispolzovanii-http-2-ili-http-3"},"modified":"2026-11-19T03:36:35","modified_gmt":"2026-11-19T01:36:35","slug":"nginx2root-nginx-vulnerabilities-allow-code-execution-when-using-http2-or-http3","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/news\/nginx2root-nginx-vulnerabilities-allow-code-execution-when-using-http2-or-http3","title":{"rendered":"NGINX2Root \u2014 zranite\u013enosti v nginx, ktor\u00e9 umo\u017e\u0148uj\u00fa vykona\u0165 k\u00f3d pri pou\u017e\u00edvan\u00ed HTTP\/2 alebo HTTP\/3","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Spolo\u010dnos\u0165 Xint odhalila p\u00e4\u0165 zranite\u013enost\u00ed v nginx, ktor\u00e9 dostali k\u00f3dov\u00e9 meno NGINX2Root. Najnebezpe\u010dnej\u0161ia zranite\u013enos\u0165 (CVE-2026-123007) umo\u017e\u0148uje vykonanie k\u00f3du s pr\u00e1vami pracovn\u00e9ho procesu pri prij\u00edman\u00ed po\u017eiadaviek na serveri pomocou protokolu HTTP\/2. Ostatn\u00e9 4 probl\u00e9my taktie\u017e umo\u017e\u0148uj\u00fa vzdialen\u00e9 vykonanie k\u00f3du, ale prejavuj\u00fa sa za \u0161pecifick\u00fdch nastaven\u00ed alebo si vy\u017eaduj\u00fa osobitn\u00e9 podmienky na zneu\u017eitie. Okrem toho v\u00fdskumn\u00edci zo spolo\u010dnosti Xint objavili nov\u00fa zranite\u013enos\u0165 v subsyst\u00e9me SCTP jadra Linuxu, ktor\u00e1 umo\u017e\u0148uje lok\u00e1lnemu pou\u017e\u00edvate\u013eovi z\u00edska\u0165 pr\u00e1va roota v syst\u00e9me a ob\u00eds\u0165 izol\u00e1ciu kontajnerov. Pre v\u0161etky 5 zranite\u013enost\u00ed v nginx boli vyvinut\u00e9 exploity, ktor\u00e9 re\u0165azovo zneu\u017e\u00edvaj\u00fa zranite\u013enosti v nginx a v jadre Linuxu na vzdialen\u00e9 vykonanie k\u00f3du s pr\u00e1vami roota na Linuxovom serveri, aj ke\u010f nginx be\u017e\u00ed v Docker kontajneri.    <\/p>\n<p>Probl\u00e9my boli opraven\u00e9 vo verzi\u00e1ch nginx 1.30.7 a 1.31.9, v ktor\u00fdch bolo okrem uveden\u00fdch probl\u00e9mov odstr\u00e1nen\u00fdch \u010fal\u0161\u00edch 5 zranite\u013enost\u00ed. Stav odstr\u00e1nenia zranite\u013enost\u00ed v distrib\u00faci\u00e1ch je mo\u017en\u00e9 pos\u00fadi\u0165 na t\u00fdchto str\u00e1nkach: Debian, Ubuntu, SUSE\/openSUSE, RHEL, Gentoo, Arch, Fedora, FreeBSD, Rosa, ALT. Ako obch\u00e1dzaj\u00face opatrenie na blokovanie zranite\u013enost\u00ed sa odpor\u00fa\u010da zak\u00e1za\u0165 podporu protokolov HTTP\/2 a HTTP\/3 v nastaveniach nginx, nastaven\u00edm \u201ehttp2 off;\u201c a \u201ehttp3 off;\u201c v ka\u017edom bloku \u201eserver\u201c a skontrolova\u0165, \u010di v pr\u00edkazoch listen nie s\u00fa parametre \u201ehttp2\u201c a \u201equic\u201c, ako aj odstr\u00e1ni\u0165 nastavenia sp\u00f4sobuj\u00face rozl\u00ed\u0161enie mien hostite\u013eov v DNS po\u010das spracovania po\u017eiadaviek (napr\u00edklad pri pou\u017eit\u00ed kon\u0161trukci\u00ed typu \u201eproxy_pass http:\/\/$host;\u201c na presmerovanie pripojen\u00ed k backendu).      <\/p>\n<p>Pokia\u013e ide o zranite\u013enos\u0165 v jadre Linux, t\u00e1to vedie k pr\u00edstupu k u\u017e uvo\u013enenej pam\u00e4ti alebo k zdvojn\u00e1sobeniu uvo\u013enenia pam\u00e4te v implement\u00e1cii protokolu SCTP. Probl\u00e9m sa prejavuje od vydania 4.15 (janu\u00e1r 2018) a zatia\u013e ost\u00e1va neopravite\u013en\u00fd. CVE nebolo pridelen\u00e9. Detaily a exploit zatia\u013e neboli verejne odhalen\u00e9. Na \u00fatok sta\u010d\u00ed pr\u00edtomnos\u0165 modulu jadra sctp v syst\u00e9me (predvolene je pr\u00edtomn\u00fd vo viacer\u00fdch distrib\u00faci\u00e1ch a automaticky sa na\u010d\u00edta pri otvoren\u00ed SCTP-socketu). Na blokovanie na\u010d\u00edtania modulu sctp sa odpor\u00fa\u010da vytvori\u0165 konfigura\u010dn\u00fd s\u00fabor \/etc\/modprobe.d\/sctp.conf obsahuj\u00faci \u201einstall sctp \/bin\/false\u201c.      <\/p>\n<p>Odhalen\u00e9 probl\u00e9my v nginx:  <\/p>\n<ul>\n<li class=\"l\"> CVE-2026-123007 \u2014 celo\u010d\u00edseln\u00e9 prete\u010denie v k\u00f3de riadenia toku HTTP\/2, ktor\u00e9 umo\u017e\u0148uje \u010d\u00edta\u0165 a zapisova\u0165 d\u00e1ta do oblasti za hranicami pridelen\u00e9ho buffera. \u010c\u00edtanie z oblasti mimo buffera umo\u017e\u0148uje ur\u010di\u0165 rozlo\u017eenie pam\u00e4te, zatia\u013e \u010do z\u00e1pis umo\u017e\u0148uje prep\u00edsa\u0165 ukazovate\u013e na funkciu uvo\u013enenia a dosiahnu\u0165 vykonanie vlastn\u00e9ho k\u00f3du s pr\u00e1vami pracovn\u00e9ho procesu. Na \u00fatok sta\u010d\u00ed povolenie spracovania po\u017eiadaviek HTTP\/2 na <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sk\/server\/dts-newyork\/\"   title=\"serveri\" data-wpil-keyword-link=\"linked\">serveri<\/a>. Probl\u00e9m sa prejavuje od vydania nginx 1.9.5 (rok 2015), v ktorom sa pridala podpora HTTP\/2. Vyu\u017e\u00edvanie zranite\u013enosti nezanech\u00e1va stopy v \u0161tandardn\u00fdch pr\u00edstupov\u00fdch logoch, ale nepriame znaky pokusu o \u00fatok m\u00f4\u017eu sved\u010di\u0165 o havarijn\u00fdch ukon\u010deniach pracovn\u00fdch procesov (segfault) v chybov\u00fdch logoch a anom\u00e1lne vysok\u00fd prich\u00e1dzaj\u00faci prenos z jedn\u00e9ho IP.\n<li class=\"l\"> CVE-2026-123633 \u2014 pr\u00edstup k pam\u00e4ti po jej uvo\u013enen\u00ed po\u010das spracovania pripojen\u00ed HTTP\/2, k \u010domu doch\u00e1dza, ke\u010f sa akt\u00edvne pripojenie omylom umiestni do frontu na uvo\u013enenie, ale upstream modul s n\u00edm st\u00e1le pracuje. Probl\u00e9m sa prejavuje pri stanoven\u00ed nedostato\u010dn\u00e9ho po\u010dtu pripojen\u00ed cez direkt\u00edvu worker_connections a pri pou\u017eit\u00ed direkt\u00edv proxy_pass, fastcgi_pass alebo grpc_pass.\n<li class=\"l\"> CVE-2026-121810 \u2014 pr\u00edstup k pam\u00e4ti po jej uvo\u013enen\u00ed v k\u00f3de spracovania HTTP\/3 (QUIC), ktor\u00fd nast\u00e1va pri uzatv\u00e1ran\u00ed QUIC pripojenia, ak jeden z HTTP\/3 po\u017eiadaviek na\u010falej pokra\u010duje. Zranite\u013enos\u0165 sa prejavuje pri preposielan\u00ed po\u017eiadaviek na backend pomocou direkt\u00edv proxy_pass, fastcgi_pass alebo grpc_pass.\n<li class=\"l\"> CVE-2026-123634 \u2014 pr\u00edstup k pam\u00e4ti po jej uvo\u013enen\u00ed v k\u00f3de DNS resolvera. Zranite\u013enos\u0165 sa prejavuje v konfigur\u00e1ci\u00e1ch s direkt\u00edvou \u201eresolver\u201c alebo pri pou\u017eit\u00ed direkt\u00edv \u201emirror\u201c a \u201eproxy_pass\u201c s dynamick\u00fdm preposielan\u00edm na backend na z\u00e1klade n\u00e1zvu hostite\u013ea (proxy_pass http:\/\/$host), ak hlavn\u00e9 a zrkadlen\u00e9 po\u017eiadavky o\u010dak\u00e1vaj\u00fa rovnak\u00fa DNS odpove\u010f.\n<li class=\"l\"> CVE-2026-113425 \u2014 pr\u00edstup k pam\u00e4ti po jej uvo\u013enen\u00ed v mail proxy, ktor\u00fd sa prejavuje pri pou\u017eit\u00ed nastaven\u00ed \u201eproxy on\u201c a \u201eauth_http\u201c v bloku \u201email\u201c. Probl\u00e9m je sp\u00f4soben\u00fd t\u00fdm, \u017ee uzavretie klientsk\u00e9ho pripojenia uvo\u013e\u0148uje rel\u00e1ciu, ale pripojenie k autentifika\u010dnej slu\u017ebe zost\u00e1va otvoren\u00e9 a v procese jeho spracovania sa uskuto\u010d\u0148uje pr\u00edstup k u\u017e uvo\u013enenej pam\u00e4ti.    <\/ul>\n<p>Ostatn\u00e9 zranite\u013enosti opraven\u00e9 v nginx 1.30.7 a 1.31.9:  <\/p>\n<ul>\n<li class=\"l\"> CVE-2026-125283 \u2014 prete\u010denie bufferu, ktor\u00e9 sa prejavuje pri s\u00fa\u010dasnom pou\u017eit\u00ed direkt\u00edv \u201etry_files\u201c a \u201ealias\u201c.\n<li class=\"l\"> CVE-2026-120967 \u2014 zranite\u013enos\u0165 v module stream, umo\u017e\u0148uj\u00faca overenie klientsk\u00e9ho TLS certifik\u00e1tu v kontexte nastaven\u00ed. <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sk\/server\/dts-los-angeles\/\"   title=\"servera\" data-wpil-keyword-link=\"linked\">servera<\/a> predvolene, namiesto virtu\u00e1lneho hostite\u013ea pri s\u00fa\u010dasnom ukon\u010den\u00ed rokovania TLS spojen\u00ed.\n<li class=\"l\"> CVE-2026-120993 \u2014 dereferencovanie nulov\u00e9ho ukazovate\u013ea, ktor\u00e9 sa prejavuje pri pou\u017eit\u00ed druhej verzie protokolu PROXY v konfigur\u00e1ci\u00e1ch s dynamick\u00fdm na\u010d\u00edtan\u00edm TLS certifik\u00e1tov. Probl\u00e9m m\u00f4\u017ee vies\u0165 k hav\u00e1rii pracovn\u00e9ho procesu.\n<li class=\"l\"> CVE-2026-123640 \u2014 ob\u00eddenie obmedzen\u00ed v module ngx_stream_ssl_preread_module prostredn\u00edctvom prenosu \u0161peci\u00e1lne form\u00e1tovan\u00fdch TLS spr\u00e1v ClientHello.\n<li class=\"l\"> CVE-2026-118899 \u2014 nekone\u010dn\u00e9 slu\u010dkovanie v pracovnom procese pri \u010d\u00edtan\u00ed tela po\u017eiadavky nad SSL.    <\/ul>\n<p>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/www.opennet.ru\/opennews\/art.shtml?num=66717\">opennet.ru<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Xint \u0432\u044b\u044f\u0432\u0438\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0432 nginx, \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043f\u0440\u0438\u0441\u0432\u043e\u0435\u043d\u043e \u043a\u043e\u0434\u043e\u0432\u043e\u0435 \u0438\u043c\u044f NGINX2Root. \u041d\u0430\u0438\u0431\u043e\u043b\u0435\u0435 \u043e\u043f\u0430\u0441\u043d\u0430\u044f \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u044c (CVE-2026-123007) \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u0435\u0442 \u0434\u043e\u0431\u0438\u0442\u044c\u0441\u044f \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u044f \u043a\u043e\u0434\u0430 \u0441 \u043f\u0440\u0430\u0432\u0430\u043c\u0438 \u0440\u0430\u0431\u043e\u0447\u0435\u0433\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u0430 \u043f\u0440\u0438 \u043f\u0440\u0438\u0451\u043c\u0435 \u043d\u0430 \u0441\u0435\u0440\u0432\u0435\u0440\u0435 \u0437\u0430\u043f\u0440\u043e\u0441\u043e\u0432 \u0441 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0435\u043c \u043f\u0440\u043e\u0442\u043e\u043a\u043e\u043b\u0430 HTTP\/2. \u041e\u0441\u0442\u0430\u043b\u044c\u043d\u044b\u0435 4 \u043f\u0440\u043e\u0431\u043b\u0435\u043c\u044b \u0442\u0430\u043a\u0436\u0435 \u0434\u043e\u043f\u0443\u0441\u043a\u0430\u044e\u0442 \u0443\u0434\u0430\u043b\u0451\u043d\u043d\u043e\u0435 \u0432\u044b\u043f\u043e\u043b\u043d\u0435\u043d\u0438\u0435 \u043a\u043e\u0434\u0430, \u043d\u043e \u043f\u0440\u043e\u044f\u0432\u043b\u044f\u044e\u0442\u0441\u044f \u043f\u0440\u0438 \u043d\u0430\u043b\u0438\u0447\u0438\u0438 \u0441\u043f\u0435\u0446\u0438\u0444\u0438\u0447\u043d\u044b\u0445 \u043d\u0430\u0441\u0442\u0440\u043e\u0435\u043a \u0438\u043b\u0438 \u0442\u0440\u0435\u0431\u0443\u044e\u0442 \u043e\u0441\u043e\u0431\u044b\u0445 \u0443\u0441\u043b\u043e\u0432\u0438\u0439 \u0434\u043b\u044f \u044d\u043a\u0441\u043f\u043b\u0443\u0430\u0442\u0430\u0446\u0438\u0438. \u041f\u043e\u043c\u0438\u043c\u043e \u044d\u0442\u043e\u0433\u043e, [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[702],"tags":[],"class_list":["post-184322","post","type-post","status-publish","format-standard","hentry","category-news"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Xint \u0432\u044b\u044f\u0432\u0438\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0432 nginx, \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043f\u0440\u0438\u0441\u0432\u043e\u0435\u043d\u043e \u043a\u043e\u0434\u043e\u0432\u043e\u0435 \u0438\u043c\u044f NGINX2Root.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Alexander Kovalev\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/news\/nginx2root-nginx-vulnerabilities-allow-code-execution-when-using-http2-or-http3\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47NGINX2Root \u2014 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0432 nginx, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0438\u0435 \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c \u043a\u043e\u0434 \u043f\u0440\u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0438 HTTP\/2 \u0438\u043b\u0438 HTTP\/3 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Xint \u0432\u044b\u044f\u0432\u0438\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0432 nginx, \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043f\u0440\u0438\u0441\u0432\u043e\u0435\u043d\u043e \u043a\u043e\u0434\u043e\u0432\u043e\u0435 \u0438\u043c\u044f NGINX2Root.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/news\/nginx2root-nginx-vulnerabilities-allow-code-execution-when-using-http2-or-http3\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-11-19T01:36:31+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-19T01:36:35+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47NGINX2Root \u2014 zranite\u013enosti v nginx, ktor\u00e9 umo\u017e\u0148uj\u00fa vykonanie k\u00f3du pri pou\u017e\u00edvan\u00ed HTTP\/2 alebo HTTP\/3 | ProHoster","description":"Spolo\u010dnos\u0165 Xint identifikovala p\u00e4\u0165 zranite\u013enost\u00ed v nginx, ktor\u00fdm bolo priraden\u00e9 k\u00f3dov\u00e9 meno NGINX2Root.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/news\/nginx2root-nginx-vulnerabilities-allow-code-execution-when-using-http2-or-http3","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47NGINX2Root \u2014 \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0438 \u0432 nginx, \u043f\u043e\u0437\u0432\u043e\u043b\u044f\u044e\u0449\u0438\u0435 \u0432\u044b\u043f\u043e\u043b\u043d\u0438\u0442\u044c \u043a\u043e\u0434 \u043f\u0440\u0438 \u0438\u0441\u043f\u043e\u043b\u044c\u0437\u043e\u0432\u0430\u043d\u0438\u0438 HTTP\/2 \u0438\u043b\u0438 HTTP\/3 | ProHoster","og:description":"\u041a\u043e\u043c\u043f\u0430\u043d\u0438\u044f Xint \u0432\u044b\u044f\u0432\u0438\u043b\u0430 \u043f\u044f\u0442\u044c \u0443\u044f\u0437\u0432\u0438\u043c\u043e\u0441\u0442\u0435\u0439 \u0432 nginx, \u043a\u043e\u0442\u043e\u0440\u044b\u043c \u043f\u0440\u0438\u0441\u0432\u043e\u0435\u043d\u043e \u043a\u043e\u0434\u043e\u0432\u043e\u0435 \u0438\u043c\u044f NGINX2Root.","og:url":"https:\/\/prohoster.info\/sk\/blog\/news\/nginx2root-nginx-vulnerabilities-allow-code-execution-when-using-http2-or-http3","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2026-11-19T01:36:31+00:00","article:modified_time":"2026-11-19T01:36:35+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":[],"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/184322","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=184322"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/184322\/revisions"}],"predecessor-version":[{"id":184323,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/184322\/revisions\/184323"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=184322"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=184322"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=184322"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}