SASEUL PHP Security Update Notice: No Impact If Your Mining Address Is a Separate Wallet, the Team Says

· Holder guide

SASEUL PHP security update notice: is there anything for me to do?

The notice's to-do list is for people who run a node on their own PHP

PHP security issue

New PHP versions announced, October 21, 2026

SASEUL notice #86

October 22: scope of impact and recommendations

Pool miners who only mine

The guide's method has no PHP install step

People running their own node

Use a separate wallet for the mining address, update PHP to a new version

Based on SASEUL official Telegram notice #86 (October 22, 2026). Read from left to right. The darker box is the group the notice gives direct instructions to.

A notice titled "SASEUL Notice: PHP security update" was posted on the official SASEUL Telegram notice channel. It went up at 5:04 PM Korean time (KST) on October 22, 2026. A security issue was announced for PHP (a program many website servers use), so the SASEUL team explained how far it reaches into SASEUL and told people who run a node (a computer that holds and passes around a share of the ledger) on their own PHP what to do. The advice is to use a separate wallet for the mining address and to update PHP to a fixed version. If you only run a mining program in a pool, the notice doesn't seem to ask you to do anything directly.

What is this notice? It explains how far the PHP security issue reaches into SASEUL

On October 21, 2026, the official PHP website posted a security announcement along with news of new versions that fix two security issues (vulnerabilities). The ChangeLog dates these versions October 22. A vulnerability is a security hole in a program, and a CVE is a shared reference number for such holes. The numbers in the notice are CVE-2026-109618 and CVE-2026-109619. The PHP website classifies both as critical and recommends that all PHP users update right away.

The SASEUL notice opens by saying the team knows many people in the SASEUL community are worried about this news. Then it lays out the scope and its recommendations. The news applies everywhere PHP is used, and the SASEUL team explained what SASEUL users should look at.

Original SASEUL official Telegram notice #86 «SASEUL Notice: PHP security update». SASEUL (Official), t.me/saseul_notice/86, Oct 22 at 17:04. No impact if the mining address is a separate wallet, update to PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12 or later recommended, new Docker image in preparation
This is the original SASEUL official Telegram notice #86 (October 22, 2026, 17:04 Korean time). Tap it to see it larger.

How far does it reach? With a separate wallet for the mining address, the notice says the node has nothing to steal

The notice names two points about the scope.

My reading of the notice's "separate wallet" is this: you don't keep the wallet's secrets (recovery phrase, private key) on the node, and you only write the coin-receiving address into the node. That explanation is my own interpretation.

What if you only run a mining program in a pool? The notice's to-do list is for people who run SASEUL on their own PHP

The method in this blog's mining guide is to join a pool (a group that mines together) with a mining program (miner.exe). Here's what I confirmed in the guide.

The people the notice tells to update are "those who run SASEUL on their own PHP." So someone who just mines in a pool as the guide describes doesn't seem to be in the group the notice directly asks to update PHP. That said, neither the notice nor the guide says how PHP is used inside the mining program, so I don't know. If you're worried, watch the official notice channel for the next announcement.

What if you run your own node? Use a separate wallet for the mining address and update PHP to a new version

The notice recommends two things.

  1. Use a separate wallet for the mining address
  2. If you run SASEUL on your own PHP, update to the fixed version that matches the one you use. The versions named in the notice are 8.2.35, 8.3.36, 8.4.27 and 8.5.12, and anything after those is fine too
PHP version you use Fixed version named in the notice
8.2 8.2.35 or later
8.3 8.3.36 or later
8.4 8.4.27 or later
8.5 8.5.12 or later

The PHP website's ChangeLog lists the same version numbers, dated October 22, 2026 (the front-page announcement is dated October 21, so the two dates are a day apart).

If you run the node from a Docker image (a way of running a program inside a container, like a separate box), the notice says the node runs in a container separated from the rest of the server. It also says a new Docker image with the fixed PHP and a SASEUL update are in preparation. The team said it will test them well and then announce them on the notice channel. It isn't out yet. It's in preparation.

So what should you do? Pool miners watch the notice channel, and node operators check two things

  1. If you only run a mining program in a pool, I didn't find anything you need to change right now. Just check, at the "Enter your wallet address and start" step of the guide, that the mining program holds only an address and not a recovery phrase or a private key
  2. If you run your own node, check that the mining address is a separate wallet
  3. If you run your node on your own PHP, check the version number, and update if it's lower than the table above
  4. If you run it from a Docker image, watch whether the notice channel posts a new image announcement. The notice only said it's in preparation
  5. Check the official notice channel. New announcements appear on the official SASEUL Telegram

Sources


I hold SL. I checked the notice against the original on the official SASEUL Telegram, and the PHP version numbers and vulnerability descriptions against the official PHP website, on October 23, 2026.

Questions after reading this

Leave a question you want answered. Useful ones are added to this post with an answer. Please do not include your name, contact details, wallet address or recovery phrase.