TRENDING
A person sweeping a metal detector across a wet sandy beach with a sea fort on the horizon
November 22, 2026
How to Write YARA Rules With YARA-X to Hunt Malicious Python .pth Startup Files and Measure False Positives Before You Trust Them
A peeling black-and-white metal door standing ajar, with a dark empty hall and bright windows beyond
November 22, 2026
AWS’s “Found a Zero-Day on Their Own” Post Never Names the Product; the Advisory Behind Its Link Shows a Server That Ships With No Login, a README Now Saying Keep It Off the Internet, and a Fix Merged October 19 That PyPI and Docker Hub Still Do Not Carry
A hand paging through index cards in an open wooden library card-catalog drawer labeled Agriculture, with a second drawer open below to the right
November 22, 2026
Microsoft Tells Customers Unauthorized Parties Read Admin Email Addresses and Tenant Metadata Through an Entra Connect Health Flaw Introduced July 23, but Gives No Tenant Count or Start Date, and Its Own Docs Send Tenant Security Notices to the Same Kinds of Contacts
Swimmers in separate lanes of a blue swimming pool, seen from above the water, with lane lines running across the picture
November 22, 2026
How to Size a PostgreSQL Connection Pool in Python: Find Where Throughput Stops Growing, Split max_connections Across Workers, and Stop Slow Handlers From Hoarding Connections
Workers in caps lean over a 1913 Ford assembly line, each assembling parts as they pass on the moving line
November 22, 2026
OpenAI’s Performance Factory Turns Regression Response Into a Task Queue for Agents, but Its Numbers Stop at 600 Root-Caused Cases in 1,700 Investigations and a 70% Grade on 100 Suggestions, and in a Toy World Each of Its Reviewer’s Two Counterfactual Questions Can Return a Confident Wrong Answer
22 Nov 2026
SXZ.io SXZ.io
  • Home
Search the Site
Popular Searches:
Technology Amazon AI
Recent Posts
The sun setting over the sea behind a pyramid-shaped stone monument at Cape Soya, the northernmost point of Japan
How to Retire an API Endpoint in FastAPI: Send Deprecation and Sunset Headers, Find the Clients Still Calling It, Schedule Brownouts, and Block an Early Removal With oasdiff
November 22, 2026
Brass sextant in an open wooden case inside a museum display, an instrument for measuring the angle to the horizon
MIT Technology Review’s “Most Misunderstood Graph” Update Reports METR’s Judgment Findings Mostly Fairly, but It Never Says Each Point Is a 50% Success Rate or Gives the New 3.6-Month Doubling Time and 2.1 to 4.9 Month Range, and It Credits OpenAI With a Comparison METR Built
November 22, 2026
Brass telescope on a wooden tripod inside a white observatory dome with the roof slit open to the sky
Rackspace Says Leaked Credentials Let an Intruder Act as Legitimate Users in Some Spot Customer Organizations and Reach Their Kubernetes Secrets, a Platform9 Co-Founder Names a Breached Observability System as the Root Cause, and the Status Page Says Only “System Maintenance Operations”
November 22, 2026
SXZ.io SXZ.io
  • Home

Categories

Articles 310 Posts
News 316 Posts
Learning Hub 282 Posts
Home/News/PHP Fixes 18 Flaws Including Seven Rated Critical, and Its Advisories Tie Three of Them to October’s PHP2Shell Release; Upload Progress Now Defaults to Off While the Shipped php.ini Templates Still Say On, and PHP 8.1 and Older Get No Upstream Patch
News

PHP Fixes 18 Flaws Including Seven Rated Critical, and Its Advisories Tie Three of Them to October’s PHP2Shell Release; Upload Progress Now Defaults to Off While the Shipped php.ini Templates Still Say On, and PHP 8.1 and Older Get No Upstream Patch

PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36 fix 18 CVEs, seven rated critical at 9.2; three build on the October PHP2Shell release, upload progress now defaults to off while the shipped php.ini templates...

November 19, 2026 12 Min Read
33

PHP released 8.5.13, 8.4.28, 8.3.37 and 8.2.36 on November 19 with fixes for 18 CVEs, and GitHub’s advisories for php-src rate seven of them Critical at CVSS 4.0 9.2. A day earlier PHP’s pre-announcement said “The issues rated CRITICAL require either non-default configuration or uncommon setups.” The advisories mostly bear that out, but they also hold details that a headline count of 18 and 7 hides.

Table Of Content

  • What shipped on November 19
  • “Non-default configuration or uncommon setups”: what the score says and what the text says
  • FPM request smuggling, CVE-2026-129289
  • Timezone cache, CVE-2026-129496
  • Session files, CVE-2026-126714
  • Magic-method backtrace, CVE-2026-129474
  • Three of the seven build on October’s release
  • A default changes in a patch release
  • Who is exposed
  • Distribution and third-party fixes
  • Exploitation and public code at about 19:20 UTC
  • Who found them
  • What we would do first
  • Patch, then restart
  • Check the front end for connection reuse
  • If you cannot patch yet
  • What the sources leave open
  • Sources

Three of them stand out. By the advisories’ own words, three of the seven critical flaws are follow-ons to October’s PHP2Shell release: one is called “an incomplete fix for CVE-2026-109619”, one says “Further scenarios have been discovered” after the 8.5.12 change, and one says 8.5.12 “introduced delayed handling of this allocation failure”. The fix for CVE-2026-115560 turns session upload progress off by default, yet the php.ini templates shipped in the same releases still say “Default Value: On”. And PHP 8.1 and older get no patch, while they run on 31.5% of the WordPress sites that report a PHP version.

This post is built from primary records: php.net, the 17 GitHub security advisories for php-src, the CVE records, php-src source at the release tags, CISA’s KEV feed and the distribution trackers. Checks marked as ours ran between 19:16 and 19:30 UTC on November 19. We did not run PHP, did not fetch or run any exploit, and left out the step-by-step trigger details the advisories contain. For the October background see our posts on PHP2Shell before the patch and the fixes shipping a day early.

What shipped on November 19

php.net lists the four security releases and, on the same date, PHP 8.6.0. The 8.6.0 ChangeLog carries the same 17 advisory fixes as 8.5.13, so the new major version is not a way around the update. GitHub published the 17 advisories between 14:05:55 and 14:08:40 UTC, inside the 14:00 to 14:30 window the pre-announcement gave, and the CVE records followed between 14:41 and 14:44 UTC. The eighteenth CVE, CVE-2026-48841, is a bundled uriparser 1.0.3 upgrade in the 8.5 ChangeLog and has no advisory.

CVE What the advisory calls it Branches What the advisory says has to be true
CVE-2026-129289 PHP-FPM request smuggling through an unread HTTP request body 8.2 to 8.5; code present since PHP 5.6.0 A front end that reuses FastCGI connections (nginx with fastcgi_keep_conn on, Apache mod_proxy_fcgi with enablereuse=on, HAProxy FastCGI applications that retain backend connections, LSAPI) and an application path that opens php://input without reading it fully
CVE-2026-129496 Timezone cache use-after-free can lead to remote code execution 8.2 to 8.5; since PHP 5.3.18 and 5.4.8 A startup diagnostic written through the file-based error_log, then an early diagnostic in a fresh worker, such as the max_input_vars warning
CVE-2026-126714 Partially overwritten session files can lead to remote code execution 8.2 to 8.5; since PHP 4.1.0 The files session handler (PHP’s default), attacker-influenced session data, an interrupted write and a suitable gadget chain in the application
CVE-2026-115560 Session serializer mismatch can lead to remote code execution 8.2 to 8.5; upload progress since PHP 5.4.0 Session upload progress enabled (the default until this release), two sides using different session.serialize_handler values on one session store, and a gadget chain
CVE-2026-129481 Use-after-free after interrupted session shutdown 8.3 to 8.5 A fatal error inside a session cleanup callback, then a later request on the same worker; the reproducer used PHP-FPM with OPcache disabled
CVE-2026-129182 Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown 8.5 only A fatal diagnostic during later shutdown work, then an early diagnostic in a later request on the same worker (Apache per-directory configuration, or an FPM front end that sends PHP_VALUE or PHP_ADMIN_VALUE)
CVE-2026-129474 Use-after-free in magic method backtraces can lead to remote code execution 8.5 only fatal_error_backtraces=1 (on by default in 8.5) and zend.exception_ignore_args=0

The other ten advisories are four High (an FPM epoll use-after-free that gives local privilege escalation after code runs inside a worker, 8.8; a denial of service through folded HTTP response headers, 8.7; mixed-case HTTPS and FTPS URLs sent in plaintext, 8.2; a PHAR OpenSSL signature bypass, 7.7) and six Medium (a CGI PATH_INFO out-of-bounds read and write, two SOAP flaws, a DOM double free, an oversized-URI serialization error and a status-page XSS in FPM).

“Non-default configuration or uncommon setups”: what the score says and what the text says

All seven critical advisories carry the same CVSS 4.0 vector except for one field: network attack, no privileges, no user interaction, attack requirements present (AT:P), and high impact on confidentiality, integrity and availability. Four set attack complexity High (CVE-2026-115560, CVE-2026-129474, CVE-2026-129481, CVE-2026-129496) and three set it Low (CVE-2026-126714, CVE-2026-129182, CVE-2026-129289). Our recomputation with the Python cvss library (version 3.6) gives 9.2 for both, and 9.3 for the Low-complexity vector if the attack requirements were absent (AT:N). So the score cannot separate a flaw that needs a file-based error log from one that needs a front-end setting. Those conditions live in the advisory text, and four of them are worth reading closely.

FPM request smuggling, CVE-2026-129289

The advisory says exploitation can run attacker-controlled PHP “without another user’s interaction or a non-default PHP configuration”, so the non-default part is the front end. It adds: “It does not require memory corruption, knowledge of memory addresses or a race condition.” The code in question dates to the lazy php://input handling added in PHP 5.6.0. Patchstack, which sorts the release by what reaches WordPress, says “two of these deserve attention this week”, and this is one of its two. It writes that WordPress opens php://input on every REST request. We checked the source: the trunk copy of class-wp-rest-server.php calls $request->set_body( self::get_raw_data() ) at line 430, and get_raw_data() reads file_get_contents( 'php://input' ) at line 2165. We did not test whether that pattern leaves bytes unread. The advisory says reading the body to the end prevents the demonstrated condition, but that “error paths, resource exhaustion and application shutdown can make this unreliable as the sole mitigation”. Because file_get_contents reads the stream, the open question is what remains unread when PHP’s multipart parser stops early, as the advisory describes.

Timezone cache, CVE-2026-129496

This is the other flaw on Patchstack’s short list. The advisory sets a narrow condition: “The diagnostic must actually be written through PHP’s file-based error_log path. FPM’s own error log does not by itself meet this condition.” A crafted request has crashed an FPM worker with the default max_input_vars, and command execution was demonstrated in FPM and Apache mod_php “with known addresses and additional configuration assumptions”, with ASLR left on. The affected code has been present since PHP 5.3.18 and 5.4.8, by code inspection.

Session files, CVE-2026-126714

“This affects the files session save handler, which is PHP’s default”, the advisory says, and the code has been present since PHP 4.1.0. The attack still needs attacker-influenced session data, an interrupted write and a gadget chain in the application. The fix truncates the session file before writing.

Magic-method backtrace, CVE-2026-129474

This one is PHP 8.5 only. Fatal error backtraces are on by default in 8.5, and the advisory says php.ini-production “sets zend.exception_ignore_args=1 and prevents this attack path”. We checked the 8.5.13 templates: php.ini-production has zend.exception_ignore_args = On and php.ini-development has Off. With no php.ini at all the built-in default applies, and the advisory says “PHP’s built-in default also includes arguments”.

Three of the seven build on October’s release

PHP’s October 21 release (8.5.12, 8.4.27, 8.3.36, 8.2.35) fixed the two PHP2Shell flaws, CVE-2026-109618 and CVE-2026-109619. Three of the new critical advisories refer back to it:

CVE What the advisory says CVE ID reserved (UTC)
CVE-2026-129481 “This is an incomplete fix for CVE-2026-109619”; affects PHP 8.3 and later November 15, 13:36
CVE-2026-129182 PHP 8.5.12 fixed a generic use-after-free of the last_fatal_error_backtrace global as part of CVE-2026-109619, and “Further scenarios have been discovered” November 13, 17:51
CVE-2026-129474 “PHP 8.5.12 introduced delayed handling of this allocation failure, allowing the fatal error to be reported while the magic method call is being entered” November 15, 10:08

The advisories do not say the October fix was wrong. They describe gaps around it. The three CVE IDs were reserved 23 to 25 days after the October release, and the fixes shipped 29 days after it. The two October flaws are in CISA’s KEV catalog (added October 26, due October 29), and FIRST’s EPSS shows 0.99999 for both. The seven new critical flaws are not in the catalog at our check, and EPSS had no rows for any of the 17 new CVEs at 19:18 UTC.

CVE-2026-115560 has its own history. PHP’s October 23 informational advisory said “We suggest you set session.upload_progress.enabled=0 until the next regular bugfix release, to fully protect from an unlikely RCE vector”, and promised a full advisory “with the next release”. The flaw is now rated Critical 9.2 with attack complexity High, and it is the one with a default change attached.

A default changes in a patch release

The advisory for CVE-2026-115560 says: “The fix disables session upload progress by default and rejects runtime changes to session settings, including session.serialize_handler, while upload progress is enabled.” It adds: “Check for existing configuration that explicitly enables it, because an explicit setting overrides the new default.” We confirmed both changes in ext/session/session.c at the release tags:

Tag Default of session.upload_progress.enabled Error “Session ini settings cannot be changed at runtime when session.upload_progress.enabled is On”
php-8.2.35, 8.3.36, 8.4.27, 8.5.12 “1” absent
php-8.2.36, 8.3.37, 8.4.28, 8.5.13 “0” present (a thrown Error, when the setting is changed at runtime while upload progress is on)
master “0” present

What the sample configuration says is less clear. In php.ini-production at 8.4.28, 8.5.13 and master, the entry still reads:

; Enable upload progress tracking in $_SESSION
; Default Value: On
; Development Value: On
; Production Value: On
; https://php.net/session.upload-progress.enabled
;session.upload_progress.enabled = On

The production template is byte-identical to the previous release’s in both pairs we compared (8.4.27 with 8.4.28, and 8.5.12 with 8.5.13), and php.ini-development carries the same sample line. So the documented default is now the opposite of the compiled one, and uncommenting that line, which looks like a way to confirm the default, turns the feature back on. For most sites the new default is the safer state. For sites that use upload progress for a progress bar, it silently stops working until someone enables it, and when they do, session settings changed with ini_set() will throw. The advisory also warns: “all readers and writers of the session data it can access must use the same session.serialize_handler, even after the update.”

Who is exposed

Patchstack’s verdict on the list is “Nothing here is common, and most of it stays rare even with an unusual plugin or code layout.” That reads the release against a stock WordPress install. The advisories’ ranges are wider: two list PHP 8.1 with no patched version (CVE-2026-129291 from 8.1.20 and CVE-2026-127960 from 8.1.32), and ten give the 8.2 range as “< 8.2.36” with no lower bound. The WordPress.org PHP statistics API at 19:16 UTC showed this split:

PHP branch Share of WordPress sites reporting it Fix in this release
8.5 6.8% 8.5.13
8.4 11.1% 8.4.28
8.3 28.8% 8.3.37
8.2 21.8% 8.2.36
8.1 8.9% none
8.0 3.2% none
7.4 14.1% none
7.3 and older 5.2% none

That is 31.5% of reporting sites on branches that get nothing from php.net, and a branch share is not a patched share: sites on 8.2 to 8.5 still need to be on the new point release. php.net’s supported-versions page lists security support for 8.2 until December 31, 2026.

Distribution and third-party fixes

Status at 19:16 to 19:19 UTC for CVE-2026-129289 (Ubuntu and Red Hat were also checked for CVE-2026-129496):

  • Debian: bookworm-security lists php8.2 8.2.36-1~deb12u1 and trixie-security lists php8.4 8.4.28-1~deb13u1 as fixed; sid and forky at 8.4.27-1 were still vulnerable.
  • Amazon Linux: advisories ALAS2023-2026-3504 (php8.2), 3505 (php8.3), 3507 (php8.4) and 3506 (php8.5) are dated November 19; php8.1 on Amazon Linux 2023 is “No Fix Planned”.
  • Ubuntu: priority medium, with needs-triage for jammy php8.1, noble php8.3 and resolute and stonking php8.5, and no notice listed.
  • Red Hat: its security data API returned 404 for both CVEs, so no record yet.
  • Unsupported branches: BleepingComputer reports patched packages from Ondřej Surý for versions back to 5.6 and hardened images from Aikido. packages.sury.org lists php5.6 5.6.40-109 builds stamped November 19 between 10:28 and 12:01 UTC, hours before the advisories went public; we did not unpack them, so we cannot say what they contain.

Exploitation and public code at about 19:20 UTC

  • KEV and SSVC: none of the 17 CVEs is in the KEV catalog (version 2026.11.18). The CISA ADP entries in the CVE records list exploitation as “none” for all 17, and the automatable field as yes only for the folded-header denial of service, CVE-2026-127960.
  • What the advisories say was demonstrated: single-request execution for the FPM smuggling flaw, command execution with known addresses for the timezone cache flaw, and command execution through application gadget chains for CVE-2026-115560, one of them reproduced on 8.2.35, 8.3.36, 8.4.27 and 8.5.12. These are reporter demonstrations, not reports of attacks.
  • Public repositories: GitHub’s repository search (metadata only; we opened nothing) returned one repository mentioning CVE-2026-129496, created November 19, and none mentioning five of the other six new critical IDs. It returned 28 hits for CVE-2026-115560, whose number has been public since October 23. For CVE-2026-109619, three of the top four results were created within two days of the October release and now carry over a thousand stars each. That can change quickly.

Who found them

The 17 advisories credit 46 GitHub accounts. In the CVE records, CVE-2026-129289, CVE-2026-129474 and CVE-2026-127960 credit researchers as “Ada Logics / Anthropic”, alongside PHP maintainers; October’s pair credited Calif.io, Wiz and OpenAI. The CVE IDs for six of the seven critical flaws were reserved between November 11 and 15, and the shortest span from reservation to advisory is 3 days 21 hours (CVE-2026-129496, reserved November 15 at 16:49 UTC, published November 19 at 14:06 UTC). A reservation date is not a discovery date, so these spans say little about how long the bugs were known.

What we would do first

Patch, then restart

Move to the fixed release for your branch, then restart PHP-FPM or Apache so the master and every worker run the new build. PHP 8.6.0 carries the same fixes but is a major upgrade, so most production sites will want the point release. The advisory for the timezone flaw says to restart “the PHP master process and all workers” after clearing startup diagnostics, because workers inherit the stale state from the parent. Check the version your web server actually uses, since the CLI and FPM binaries can differ. None of these ran here, because this machine has no PHP. php -v, php -r and ini_get() are documented in PHP’s manual; php-fpm -v and php-fpm -i are the FPM binary’s counterparts, which we did not check against its help output:

php -v
php-fpm -v
php -r 'var_dump(ini_get("session.upload_progress.enabled"));'

Per the manual, a boolean INI value that is off comes back as an empty string or “0”, and on comes back as “1”. The CLI reads its own php.ini, so use php-fpm -i for the FPM binary’s php.ini, check the pool files for php_admin_value overrides, or load an authenticated phpinfo() page through the real front end.

Check the front end for connection reuse

For CVE-2026-129289, the first question is whether your front end keeps FastCGI connections open. nginx’s documentation gives fastcgi_keep_conn a default of off. This check runs on nginx 1.30.6 (Windows, with a two-server test file in which one location sets fastcgi_keep_conn on and the other sets nothing) and prints only the line that turns reuse on:

nginx -T 2>&1 | grep -n "fastcgi_keep_conn"
19:            fastcgi_keep_conn on;

nginx -T dumps the whole configuration, included files too, so the search covers them; a leading # means the line is commented out. In Apache, look for enablereuse=on on a ProxyPass line or in a proxy worker definition. HAProxy FastCGI setups and LSAPI are also named in the advisory. Do not expose PHP-FPM or LSAPI listeners to untrusted networks either way.

If you cannot patch yet

The advisories list these stopgaps, and Aikido says of the upload-progress one: “That setting doesn’t cover the other critical issues, so upgrade as soon as you can.” The stopgaps: turn backend connection reuse off (CVE-2026-129289); set session.upload_progress.enabled=0 administratively in every pool and virtual host that can write to a shared session directory, because “Calling ini_set() from the application is too late”; and for CVE-2026-129496, remove the configuration errors and deprecated settings that produce startup diagnostics, restart, or send errors to syslog. Separate FPM pools do not get separate session storage on their own, so give each tenant its own session.save_path. If you run 8.1 or older, plan the move now or ask your vendor what they backport.

What the sources leave open

  • Whether any of the seven critical flaws is being used in attacks. CISA’s data and the CVE records show none at our check.
  • Whether WordPress’s REST handling leaves request bytes unread for a malformed multipart body. Patchstack says WordPress meets the application condition; we confirmed the php://input read in the source but did not test the attack.
  • Whether the php.ini templates will be corrected to say Off, and whether Ubuntu and Red Hat will backport the fixes to their older PHP packages.
  • What severity the uriparser upgrade, CVE-2026-48841, carries; it has no advisory or score.

Sources

  • PHP: news archive 2026 (pre-announcement of November 18, October 21 and 23 advisories), ChangeLog 8, php-src security advisories, php-src source at the release tags, ini_get and CLI options in the manual
  • Records: CVE records CVE-2026-129289, CVE-2026-129496, CVE-2026-115560, CVE-2026-129481, CVE-2026-129182, CVE-2026-129474 and CVE-2026-126714; CISA KEV; FIRST EPSS
  • Coverage and analysis: Patchstack, Aikido, BleepingComputer, SecurityWeek
  • Distribution status: Debian, Ubuntu, Amazon Linux, packages.sury.org
  • Other: WordPress.org PHP statistics, WordPress REST server source, nginx FastCGI module documentation

Tags:

PHPPHP-FPMPHP2ShellVulnerability ManagementWordPress Security

Share

Black and white photograph of wide stone steps seen from above, each step a little lower than the one before
Previous Post

How to Take Incremental PostgreSQL 18 Backups With pg_basebackup, Restore the Chain With pg_combinebackup, and Predict How Big Each One Will Be

Workers in caps lean over a 1913 Ford assembly line, each assembling parts as they pass on the moving line
Next Post

OpenAI’s Performance Factory Turns Regression Response Into a Task Queue for Agents, but Its Numbers Stop at 600 Root-Caused Cases in 1,700 Investigations and a 70% Grade on 100 Suggestions, and in a Toy World Each of Its Reviewer’s Two Counterfactual Questions Can Return a Confident Wrong Answer

No Comment! Be the first one.

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Latest
22 Nov
How to Retire an API Endpoint in FastAPI: Send Deprecation and Sunset Headers, Find the Clients Still Calling It, Schedule Brownouts, and Block an Early Removal With oasdiff
22 Nov
MIT Technology Review’s “Most Misunderstood Graph” Update Reports METR’s Judgment Findings Mostly Fairly, but It Never Says Each Point Is a 50% Success Rate or Gives the New 3.6-Month Doubling Time and 2.1 to 4.9 Month Range, and It Credits OpenAI With a Comparison METR Built
Trending
November 22, 2026
How to Retire an API Endpoint in FastAPI: Send Deprecation and Sunset Headers, Find the Clients Still Calling It, Schedule Brownouts, and Block an Early Removal With oasdiff
November 22, 2026
MIT Technology Review’s “Most Misunderstood Graph” Update Reports METR’s Judgment Findings Mostly Fairly, but It Never Says Each Point Is a 50% Success Rate or Gives the New 3.6-Month Doubling Time and 2.1 to 4.9 Month Range, and It Credits OpenAI With a Comparison METR Built
November 22, 2026
Rackspace Says Leaked Credentials Let an Intruder Act as Legitimate Users in Some Spot Customer Organizations and Reach Their Kubernetes Secrets, a Platform9 Co-Founder Names a Breached Observability System as the Root Cause, and the Status Page Says Only “System Maintenance Operations”
November 21, 2026
How to Write YARA Rules With YARA-X to Hunt Malicious Python .pth Startup Files and Measure False Positives Before You Trust Them
November 21, 2026
AWS’s “Found a Zero-Day on Their Own” Post Never Names the Product; the Advisory Behind Its Link Shows a Server That Ships With No Login, a README Now Saying Keep It Off the Internet, and a Fix Merged October 19 That PyPI and Docker Hub Still Do Not Carry
November 21, 2026
Microsoft Tells Customers Unauthorized Parties Read Admin Email Addresses and Tenant Metadata Through an Entra Connect Health Flaw Introduced July 23, but Gives No Tenant Count or Start Date, and Its Own Docs Send Tenant Security Notices to the Same Kinds of Contacts

Related Posts

Rows of server racks in a data center representing network infrastructure targeted by botnets
News

C0XMO Botnet Shows Why Old Router Firmware Still Matters

June 7, 2026
Close-up of a USB flash drive, representing physical data-theft risk in office security incidents
News

Fake IT Support Is Now Walking Through the Front Door

June 7, 2026
A phone security app on a smartphone resting on a laptop keyboard.
News

Everest Forms Pro Flaw Is Being Exploited to Create Rogue WordPress Admins

June 7, 2026
A phone secured by a padlock, illustrating AI data-leak containment and security controls.
News

OpenAI’s Lockdown Mode Is a Data-Leak Brake, Not a Prompt-Injection Cure

June 8, 2026
SXZ.io SXZ.io
  • [email protected]

Categories

Articles
Learning Hub
News

All Rights Reserved by SXZ.io ©2026