FoxBox를 최신 상태로 유지하십시오. 보안 검토를 따르고 소프트웨어 릴리스에 대한 누적 패치를 찾으십시오.
Last verification28 October 2026
주기 검토주간
패치 선택소프트웨어 릴리스
보안 감시
Latest security publication
PHP host launcher available with instructions for goofy_pare_mod. The original PHP patch runs inside the application container; the new launcher starts from the host and keeps the original compatibility checks and recovery.
P1사용 가능한 패치
PHP 7.4 · host/container
An Ubuntu 24.04 host is a different environment from the Ubuntu 20.04 PHP application container. Running the original PHP updater in the host shell triggers its correct base guard.
벤더 버전Launcher 2026.10.27-r1
FoxBox 선택
Publish the tested host launcher for the existing PHP module. It reuses the original cumulative payload, verifies the container and package hashes, then runs the PHP update inside the container. No new PHP binaries and no host OS upgrade.
Real offline update and rollback passed in an isolated synthetic application. The host launcher was also checked on the Ubuntu 24.04 demo: PHP was already current, so apply changed no packages or service processes. No customer appliance was updated remotely. This launcher covers PHP only.
릴리스 지침
업데이트 방법 및 재부팅 시점
For PHP, choose the host launcher or the original in-container method. The cumulative package and separate host OS patch keep their own procedures. Check each procedure for service interruptions and reboot requirements.
이 보고서에 대한 재시작 요구 사항
구성 요소/릴리스
어플라이언스 재부팅
서비스/현재 상태
PHP 7.4 · host/containerLauncher 2026.10.27-r1
No host reboot and no Docker container restart.
If PHP needs updating, Apache inside the container stops and starts. Schedule maintenance. Persistent PHP CLI services are drained/reloaded separately if reported.
PHP · start from the Docker host · 2026.10.27-r1 · PHP host launcher
No host reboot and no Docker container restart.
If PHP needs updating, Apache inside the container stops and starts. Schedule maintenance. Persistent PHP CLI services are drained/reloaded separately if reported.
Maintenance window: Apache stop/start if PHP changes; MySQL stops and the identified writer containers are suspended during database staging. Persistent PHP CLI services require their application manager. Never use killall.
FoxBox 호스트 보안 업데이트 · 2026.10.19-r2
새 커널을 활성화하고 해당 OpenSSL 업데이트 후에 필요합니다. 결과에서 reboot_required를 확인하십시오. 프로그램은 자동으로 재부팅되지 않습니다.
패키지 스크립트로 인해 서비스가 재시작될 수 있습니다. SSH를 새로 고치고 새 연결을 확인하세요. 업데이트된 라이브러리를 사용하는 애플리케이션을 다시 시작하세요. 유지 관리 기간을 예약하세요.
PHP 7.4 · host/containerLauncher 2026.10.27-r1단계 보기 +
Run these commands on the Docker HOST, including Ubuntu 24.04. PHP remains inside goofy_pare_mod: the launcher checks that the application container is Ubuntu 20.04 amd64 with Apache/PHP 7.4. The original cumulative package dated 26 October is also required.
어플라이언스 재부팅
No host reboot and no Docker container restart.
서비스 중단
If PHP needs updating, Apache inside the container stops and starts. Schedule maintenance. Persistent PHP CLI services are drained/reloaded separately if reported.
On the Docker host, download the original cumulative ZIP 2026.10.26-r1 from its card below and the new PHP host launcher ZIP. Compare each SHA-256 with the value shown on this page, then extract them into two separate folders. Do not edit the original updater or its Ubuntu check.
Put the extracted cumulative files in a folder named foxbox-cumulative-update-2026.10.26-r1. From the parent folder, copy only the new launcher into it and enter that folder. Leave foxbox_php74.py, vendor and tools unchanged.
cp foxbox-php74-host-launcher-2026.10.27-r1/foxbox_php74_host.py foxbox-cumulative-update-2026.10.26-r1/
cd foxbox-cumulative-update-2026.10.26-r1
Still on the HOST, identify the application environment. The default container name is goofy_pare_mod. Diagnose only reads the container and does not stage or install packages. Check application.os.version_id=20.04 and architecture=amd64. Ubuntu 24.04 on the HOST is allowed.
sudo python3 foxbox_php74_host.py diagnose
Run the actual PHP check from the HOST. The launcher verifies the original bundle, copies only the public PHP payload into a private container folder if needed and runs the original check there. update_required / exit 2 means an update is needed; it is not an APT failure. Do not chain check and apply with &&.
sudo python3 foxbox_php74_host.py check
Prepare console access, a maintenance window and protected recovery for this appliance. Apply uses the original customer-specific package/configuration backup and local APT plan. Apache is restarted only when PHP changes. No real SMS/email test send is needed.
Verify from the HOST. Keep the private checkpoint in the container and a verified protected external copy. If cli_restart_required=true, drain and reload the affected PHP CLI services with their application manager, then repeat check and verify. Never use killall.
sudo python3 foxbox_php74_host.py verify
If the real application container has a different name, use --container REAL_NAME consistently on every command. If the launcher is outside the original cumulative folder, add --bundle /path/to/foxbox-cumulative-update-2026.10.26-r1. A different container OS/base remains blocked.
For an intentional recovery only, run rollback from the HOST in maintenance. The original updater verifies post-update hashes before restoring that appliance’s previous PHP packages/configuration. A later change blocks rollback. Restoring old packages reopens the vulnerabilities.
완료 확인: The PHP receipt must report the current web runtime and no pending old CLI runtime. Only PHP is covered by this launcher. CA, MySQL and zlib keep the separate scopes and instructions of the original cumulative release; PHP success is not an overall security PASS.
장치 업데이트
릴리스 라인별 하나의 누적 패치
FoxBox 소프트웨어 기준선에 사용할 패키지를 선택하십시오. 각 새로운 누적 패치는 해당 라인에서 이전에 필요한 모든 수정 사항을 확인하므로 이전 패치 레벨부터 시작할 수 있습니다. 새로운 FoxBox 소프트웨어 버전은 별도의 라인에서 시작됩니다.
01
릴리스 버전을 식별합니다.
모델명만으로는 충분하지 않습니다. 릴리스 노트에서 FoxBox 소프트웨어 버전, 운영 체제 및 하드웨어 요구 사항을 확인하십시오.
02
모든 필수 조건을 확인하십시오.
최신 패키지는 전체 누적 세트를 검사하고 지원되지 않는 기준선 또는 충족되지 않은 요구 사항에서 중지됩니다. 다른 릴리스 라인의 패치는 호환되지 않습니다.
03
적용 및 확인
백업, 유지 관리 및 복구에 대한 패키지 지침을 따르십시오. 커널 변경 사항은 업데이트를 완료하기 전에 재부팅 및 호환되는 타사 모듈이 필요합니다.
Where do I run the PHP patch?
The host and the application container can use different Ubuntu releases. In this setup the host is Ubuntu 24.04 and PHP is in goofy_pare_mod. Choose one PHP method:
PHP method
Where to run it
Original PHP updater · cumulative 26 Octoberfoxbox_php74.py / update-foxbox.sh app
INSIDE the Ubuntu 20.04 application container containing PHP.
New PHP host launcherfoxbox_php74_host.py
On the Docker HOST, including Ubuntu 24.04. It executes the original PHP updater inside goofy_pare_mod.
If the original PHP script reports “Supported base: Ubuntu20.04” from an Ubuntu 24.04 host shell, use the host launcher or enter the application container. Do not remove the OS guard. This distinction concerns PHP/app: the cumulative MySQL module and the separate host OS patches retain their own host-side procedures.
Use the PHP patch from the host shell, including an Ubuntu 24.04 host. The existing PHP 7.4 update runs inside the supported Ubuntu 20.04 container. Choose this host method or the original in-container PHP method.
패키지2026.10.27-r1 · PHP host launcher
사용 가능한 패치
Add-on for the original 2026.10.26-r1 package, not a replacement cumulative ZIP. Includes the full launcher source and instructions. Published here on 28 October.
릴리스 사용 방법 2026.10.27-r1 · PHP host launcher단계 보기 +
Run these commands on the Docker HOST, including Ubuntu 24.04. PHP remains inside goofy_pare_mod: the launcher checks that the application container is Ubuntu 20.04 amd64 with Apache/PHP 7.4. The original cumulative package dated 26 October is also required.
어플라이언스 재부팅
No host reboot and no Docker container restart.
서비스 중단
If PHP needs updating, Apache inside the container stops and starts. Schedule maintenance. Persistent PHP CLI services are drained/reloaded separately if reported.
On the Docker host, download the original cumulative ZIP 2026.10.26-r1 from its card below and the new PHP host launcher ZIP. Compare each SHA-256 with the value shown on this page, then extract them into two separate folders. Do not edit the original updater or its Ubuntu check.
Put the extracted cumulative files in a folder named foxbox-cumulative-update-2026.10.26-r1. From the parent folder, copy only the new launcher into it and enter that folder. Leave foxbox_php74.py, vendor and tools unchanged.
cp foxbox-php74-host-launcher-2026.10.27-r1/foxbox_php74_host.py foxbox-cumulative-update-2026.10.26-r1/
cd foxbox-cumulative-update-2026.10.26-r1
Still on the HOST, identify the application environment. The default container name is goofy_pare_mod. Diagnose only reads the container and does not stage or install packages. Check application.os.version_id=20.04 and architecture=amd64. Ubuntu 24.04 on the HOST is allowed.
sudo python3 foxbox_php74_host.py diagnose
Run the actual PHP check from the HOST. The launcher verifies the original bundle, copies only the public PHP payload into a private container folder if needed and runs the original check there. update_required / exit 2 means an update is needed; it is not an APT failure. Do not chain check and apply with &&.
sudo python3 foxbox_php74_host.py check
Prepare console access, a maintenance window and protected recovery for this appliance. Apply uses the original customer-specific package/configuration backup and local APT plan. Apache is restarted only when PHP changes. No real SMS/email test send is needed.
Verify from the HOST. Keep the private checkpoint in the container and a verified protected external copy. If cli_restart_required=true, drain and reload the affected PHP CLI services with their application manager, then repeat check and verify. Never use killall.
sudo python3 foxbox_php74_host.py verify
If the real application container has a different name, use --container REAL_NAME consistently on every command. If the launcher is outside the original cumulative folder, add --bundle /path/to/foxbox-cumulative-update-2026.10.26-r1. A different container OS/base remains blocked.
For an intentional recovery only, run rollback from the HOST in maintenance. The original updater verifies post-update hashes before restoring that appliance’s previous PHP packages/configuration. A later change blocks rollback. Restoring old packages reopens the vulnerabilities.
완료 확인: The PHP receipt must report the current web runtime and no pending old CLI runtime. Only PHP is covered by this launcher. CA, MySQL and zlib keep the separate scopes and instructions of the original cumulative release; PHP success is not an overall security PASS.
IMPORTANT — Latest customer cumulative security update
Ubuntu 20.04 LTS · amd64 · Apache/PHP 7.4
Original cumulative release: the app/PHP/CA commands run INSIDE the application container when present. Run its MySQL module on the Docker HOST. For PHP-only operation from the host, use the separate launcher above.
패키지Cumulative · 2026.10.26-r1
사용 가능한 패치
Complete offline binaries and automatic scripts. Read the procedure: the application and MySQL run in different environments. Focal zlib is explicitly pending; no overall security PASS is claimed.
Original 26 October cumulative: Ubuntu 20.04 amd64 Apache/PHP 7.4 in the application environment. The app commands below belong INSIDE the container when PHP is containerized. MySQL commands belong on the Docker HOST.
어플라이언스 재부팅
Not required. No automatic appliance reboot.
서비스 중단
Maintenance window: Apache stop/start if PHP changes; MySQL stops and the identified writer containers are suspended during database staging. Persistent PHP CLI services require their application manager. Never use killall.
Download the latest cumulative ZIP and verify its published SHA-256 before extraction. Inside the extracted directory verify every included file. The original PHP/CA packages and the complete MySQL 8.4.13 image are included; no update-time download is required.
sha256sum -c SHA256SUMS
Prepare console access, a maintenance window, sufficient backup/Docker storage and a protected external backup. Identify and safely drain ALL database writers and administrators, including external jobs and services. Read README-EN.txt for compatibility, private recovery and unsupported layouts.
Run the application check where PHP is installed, as root; inside the application container when present. Optional extensions are detected, newer packages are preserved.
sudo sh ./update-foxbox.sh app check
After preparing recovery, update missing PHP/CA packages. The updater backs up that appliance’s original packages and configuration, checks a local-only APT plan and restarts Apache only if PHP changes. CA changes rebuild system trust and preserve local CA files.
sudo sh ./update-foxbox.sh app apply --recovery-ready
Verify PHP and active CA revocation. If cli_restart_required=true, drain/reload persistent PHP CLI services through their actual application manager and repeat check. Verify TLS paths after CA revocation. Exit3 / PARTIAL_VENDOR_ZLIB_PENDING is deliberate: Canonical has not qualified a Focal zlib fix.
sudo sh ./update-foxbox.sh app verify
On the Docker host, replace foxbox-db and foxbox-app with actual container names and list every writer. Stage the MySQL update. If the default bridge is attached, first verify that its dynamic address is not used as a fixed endpoint, then add --default-bridge-address-dynamic. No implicit branch migration.
sh ./update-foxbox.sh mysql check --db-container foxbox-db
sh ./update-foxbox.sh mysql apply --db-container foxbox-db --writers foxbox-app --maintenance-ready
STAGED_READ_ONLY keeps writers suspended. The script preserves the original container/volume, creates logical and cold physical backups, restores into a new volume, preserves MEMORY data and the original server/client configuration, then checks the upgraded server, tables, networks and ports. Verify and copy the private checkpoint to protected external storage before reopening writes. Use the same operator/home throughout.
sh ./update-foxbox.sh mysql verify --db-container foxbox-db
After validation, commit reopens writes and resumes the listed containers. Check actual application daemons, login, read-only database access and queue health. Never generate real test messages/orders. From commit onward automatic rollback is blocked to protect newer transactions.
sh ./update-foxbox.sh mysql commit --db-container foxbox-db
sh ./update-foxbox.sh mysql verify --db-container foxbox-db
App recovery restores the customer’s original packages only if post-update hashes still match. MySQL rollback is available only before commit, with writers still suspended: it restores the original image and original volume, including MEMORY contents. It never starts an older MySQL on upgraded data. After writes resume a separate recovery plan must preserve newer transactions.
sudo sh ./update-foxbox.sh app rollback --recovery-ready
# MySQL: only BEFORE commit / solo PRIMA della commit
sh ./update-foxbox.sh mysql rollback --db-container foxbox-db --maintenance-ready
완료 확인: PHP/CA and MySQL have separate verification receipts. Focal zlib remains UNKNOWN until Canonical publishes an applicable fix; no overall security PASS is claimed. Preserve private recovery and previous download versions. No automatic host reboot.
FoxBox 호스트 보안 업데이트
Ubuntu 24.04 LTS · amd64
2026년 9월 7일~10월 18일 주간 검토의 누적 요구 사항: OpenSSH, curl, urllib3, PolicyKit, nginx, sudo, libxml2, OpenSSL, Expat 및 OpenVPN(설치된 경우). 커널 GA 일반 6.8에는 별도의 재부팅 및 모듈 검사가 있습니다. 데이터베이스 및 컨테이너는 자체 업데이트 절차를 사용합니다.
패키지2026.10.19-r2
사용 가능한 패치
패치는 적용 가능한 Ubuntu 호스트 패키지를 업데이트하고 이 라인의 이전 요구 사항을 모두 확인합니다. 기존 패키지는 유지됩니다. 프로그램은 필요한 재부팅을 보고하며 자동으로 재부팅되지 않습니다.
설치된 버전과 지원되는 기준선을 확인하십시오. 로컬 보고서는 업데이트할 패키지와 재부팅이 필요한지 여부를 식별합니다. 필수 조건 및 복구에 대한 자세한 내용은 README-EN.txt 파일을 참조하십시오.
/usr/bin/python3 foxbox_security.py check
유지 관리 기간, 두 번째 관리자 연결 및 콘솔/복구 액세스를 준비합니다. 변경 사항을 적용하려면 루트 권한, python3-apt가 설치된 시스템 Python, 인증된 Ubuntu 저장소, 일관된 dpkg 상태 및 보호된 백업을 위한 2GiB의 여유 공간이 필요합니다. 커널 설치에는 /boot에 1GiB의 여유 공간과 지원되는 인트리 모듈도 필요합니다. 필요한 버전 미만의 패키지, DKMS, 외부 모듈, HWE 커널 또는 사용할 수 없는 복구 패키지가 있는 경우 작업이 중단됩니다.
누적 패치를 적용합니다. 설치 전에 버전, 패키지 소스 및 APT 계획을 확인합니다. 필요한 모든 패키지가 이미 최신 상태인 경우 already_up_to_date를 반환합니다. 이전 패치 ZIP 파일은 필요하지 않습니다.
sudo /usr/bin/python3 foxbox_security.py apply
결과에서 packages_changed, reboot_required, reboot_performed 및 private_snapshot 값을 읽으십시오. 구성 확인이 성공적으로 완료되면 SSH를 새로 고치고, 새 독립 SSH 연결을 열어 영향을 받는 서비스를 확인하십시오. reboot_required가 true이면 유지 관리 기간에 제어된 재부팅을 수행한 다음 커널, 모뎀 경로 및 애플리케이션을 확인하십시오. 다시 검사를 실행하십시오.
완료 확인: 종료 코드 0: 검사 완료 또는 적용 성공/이미 최신 상태; 2: 검사에 조치 또는 재부팅이 필요합니다. 3: 지원되지 않는 기준선입니다. 4: 오류가 발생했거나 필수 구성 요소가 누락되었습니다. 적용 시 부분적인 변경 사항이 보고되면 개인 스냅샷을 유지하고 다시 시도하기 전에 README의 복구 지침을 따르십시오.
날짜 기록
보고서 아카이브
이전 검토 내역(원래 날짜 및 구성 요소 결정 사항 포함)을 확인하세요. 최신 업데이트를 위해서는 이전 검토의 요구 사항도 확인하는 최신 누적 패치를 사용하세요.
PHP update guide: Docker host or application container보고서를 읽으십시오. +
최초 게시 위치: 28 October 2026
PHP host launcher available with instructions for goofy_pare_mod. The original PHP patch runs inside the application container; the new launcher starts from the host and keeps the original compatibility checks and recovery.
An Ubuntu 24.04 host is a different environment from the Ubuntu 20.04 PHP application container. Running the original PHP updater in the host shell triggers its correct base guard.
Publish the tested host launcher for the existing PHP module. It reuses the original cumulative payload, verifies the container and package hashes, then runs the PHP update inside the container. No new PHP binaries and no host OS upgrade.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Run these commands on the Docker HOST, including Ubuntu 24.04. PHP remains inside goofy_pare_mod: the launcher checks that the application container is Ubuntu 20.04 amd64 with Apache/PHP 7.4. The original cumulative package dated 26 October is also required.
어플라이언스 재부팅
No host reboot and no Docker container restart.
서비스 중단
If PHP needs updating, Apache inside the container stops and starts. Schedule maintenance. Persistent PHP CLI services are drained/reloaded separately if reported.
On the Docker host, download the original cumulative ZIP 2026.10.26-r1 from its card below and the new PHP host launcher ZIP. Compare each SHA-256 with the value shown on this page, then extract them into two separate folders. Do not edit the original updater or its Ubuntu check.
Put the extracted cumulative files in a folder named foxbox-cumulative-update-2026.10.26-r1. From the parent folder, copy only the new launcher into it and enter that folder. Leave foxbox_php74.py, vendor and tools unchanged.
cp foxbox-php74-host-launcher-2026.10.27-r1/foxbox_php74_host.py foxbox-cumulative-update-2026.10.26-r1/
cd foxbox-cumulative-update-2026.10.26-r1
Still on the HOST, identify the application environment. The default container name is goofy_pare_mod. Diagnose only reads the container and does not stage or install packages. Check application.os.version_id=20.04 and architecture=amd64. Ubuntu 24.04 on the HOST is allowed.
sudo python3 foxbox_php74_host.py diagnose
Run the actual PHP check from the HOST. The launcher verifies the original bundle, copies only the public PHP payload into a private container folder if needed and runs the original check there. update_required / exit 2 means an update is needed; it is not an APT failure. Do not chain check and apply with &&.
sudo python3 foxbox_php74_host.py check
Prepare console access, a maintenance window and protected recovery for this appliance. Apply uses the original customer-specific package/configuration backup and local APT plan. Apache is restarted only when PHP changes. No real SMS/email test send is needed.
Verify from the HOST. Keep the private checkpoint in the container and a verified protected external copy. If cli_restart_required=true, drain and reload the affected PHP CLI services with their application manager, then repeat check and verify. Never use killall.
sudo python3 foxbox_php74_host.py verify
If the real application container has a different name, use --container REAL_NAME consistently on every command. If the launcher is outside the original cumulative folder, add --bundle /path/to/foxbox-cumulative-update-2026.10.26-r1. A different container OS/base remains blocked.
For an intentional recovery only, run rollback from the HOST in maintenance. The original updater verifies post-update hashes before restoring that appliance’s previous PHP packages/configuration. A later change blocks rollback. Restoring old packages reopens the vulnerabilities.
완료 확인: The PHP receipt must report the current web runtime and no pending old CLI runtime. Only PHP is covered by this launcher. CA, MySQL and zlib keep the separate scopes and instructions of the original cumulative release; PHP success is not an overall security PASS.
Real offline update and rollback passed in an isolated synthetic application. The host launcher was also checked on the Ubuntu 24.04 demo: PHP was already current, so apply changed no packages or service processes. No customer appliance was updated remotely. This launcher covers PHP only.
Cumulative security update: MySQL 8.4, PHP 7.4 and CA revocation보고서를 읽으십시오. +
최초 게시 위치: 26 October 2026
Offline customer package for Ubuntu 20.04 amd64 Apache/PHP 7.4, with a separate staged MySQL 8.4 Docker module, private backups and protected recovery. Focal zlib remains under vendor evaluation.
P1 · MySQL Community8.48.4.13
The20October Critical Patch Update applies to affected Community8.4 versions through8.4.12.8.4.13 is the fixed release for this branch.
Offline8.4.13 module, cold/logical backup, isolated restore, verification and protected pre-commit rollback. Other branches or layouts require separate qualification.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Existing standalone MySQL Community8.4 Docker deployment; supported layout described in the package README.
어플라이언스 재부팅
Not required. No automatic appliance reboot.
서비스 중단
Maintenance window: Apache stop/start if PHP changes; MySQL stops and the identified writer containers are suspended during database staging. Persistent PHP CLI services require their application manager. Never use killall.
On the Docker host, replace foxbox-db and foxbox-app with actual container names and list every writer. Stage the MySQL update. If the default bridge is attached, first verify that its dynamic address is not used as a fixed endpoint, then add --default-bridge-address-dynamic. No implicit branch migration.
sh ./update-foxbox.sh mysql check --db-container foxbox-db
sh ./update-foxbox.sh mysql apply --db-container foxbox-db --writers foxbox-app --maintenance-ready
STAGED_READ_ONLY keeps writers suspended. The script preserves the original container/volume, creates logical and cold physical backups, restores into a new volume, preserves MEMORY data and the original server/client configuration, then checks the upgraded server, tables, networks and ports. Verify and copy the private checkpoint to protected external storage before reopening writes. Use the same operator/home throughout.
sh ./update-foxbox.sh mysql verify --db-container foxbox-db
After validation, commit reopens writes and resumes the listed containers. Check actual application daemons, login, read-only database access and queue health. Never generate real test messages/orders. From commit onward automatic rollback is blocked to protect newer transactions.
sh ./update-foxbox.sh mysql commit --db-container foxbox-db
sh ./update-foxbox.sh mysql verify --db-container foxbox-db
App recovery restores the customer’s original packages only if post-update hashes still match. MySQL rollback is available only before commit, with writers still suspended: it restores the original image and original volume, including MEMORY contents. It never starts an older MySQL on upgraded data. After writes resume a separate recovery plan must preserve newer transactions.
sudo sh ./update-foxbox.sh app rollback --recovery-ready
# MySQL: only BEFORE commit / solo PRIMA della commit
sh ./update-foxbox.sh mysql rollback --db-container foxbox-db --maintenance-ready
완료 확인: PHP/CA and MySQL have separate verification receipts. Focal zlib remains UNKNOWN until Canonical publishes an applicable fix; no overall security PASS is claimed. Preserve private recovery and previous download versions. No automatic host reboot.
P1 · PHP 7.4 · Ubuntu 20.047.4.3-4ubuntu2.29+esm5
CVE-2026-109618 and CVE-2026-109619 allow remote code execution in affected PHP configurations. The Ubuntu Focal fix is retained in this cumulative release.
Detect installed extensions and active runtimes; update only missing official PHP variants. Already corrected installations are verified without forced reinstall.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 20.04 amd64, Apache mod_php7.4/prefork and Ubuntu PHP 7.4 CLI. Run inside the application container when applicable.
어플라이언스 재부팅
Not required. No automatic appliance reboot.
서비스 중단
Apache stop/start only if PHP changes; reload persistent CLI services when flagged.
Run the application check where PHP is installed, as root; inside the application container when present. Optional extensions are detected, newer packages are preserved.
sudo sh ./update-foxbox.sh app check
After preparing recovery, update missing PHP/CA packages. The updater backs up that appliance’s original packages and configuration, checks a local-only APT plan and restarts Apache only if PHP changes. CA changes rebuild system trust and preserve local CA files.
sudo sh ./update-foxbox.sh app apply --recovery-ready
Verify PHP and active CA revocation. If cli_restart_required=true, drain/reload persistent PHP CLI services through their actual application manager and repeat check. Verify TLS paths after CA revocation. Exit3 / PARTIAL_VENDOR_ZLIB_PENDING is deliberate: Canonical has not qualified a Focal zlib fix.
sudo sh ./update-foxbox.sh app verify
완료 확인: All installed PHP variants and active web/CLI runtimes must be current.
P1 · Ubuntu 20.04 · CA certificates20240203~20.04.1ubuntu0.1~esm2
USN-8944-2 removes trust in emSign ECC Root CA-G3 and Comodo AAA Services root following an intermediate-certificate compromise.
Install the original Focal CA package offline and verify actual active trust, preserving local CA configuration. Review any custom copies of revoked roots.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 20.04 amd64, Apache mod_php7.4/prefork and Ubuntu PHP 7.4 CLI. Run inside the application container when applicable.
어플라이언스 재부팅
Not required. No automatic appliance reboot.
서비스 중단
Trust store rebuilt; check TLS paths and application-specific trust caches.
After preparing recovery, update missing PHP/CA packages. The updater backs up that appliance’s original packages and configuration, checks a local-only APT plan and restarts Apache only if PHP changes. CA changes rebuild system trust and preserve local CA files.
sudo sh ./update-foxbox.sh app apply --recovery-ready
Verify PHP and active CA revocation. If cli_restart_required=true, drain/reload persistent PHP CLI services through their actual application manager and repeat check. Verify TLS paths after CA revocation. Exit3 / PARTIAL_VENDOR_ZLIB_PENDING is deliberate: Canonical has not qualified a Focal zlib fix.
sudo sh ./update-foxbox.sh app verify
완료 확인: Both compromised roots must be absent from active system trust; custom copies require review.
P2 · Ubuntu 20.04 · zlibCVE-2026-85091
Heap buffer overflow. Canonical lists Focal as Needs evaluation. USN-8954-1 provides a Noble fix; it does not specify a corrected Focal package. Embedded copies in rsync, klibc and zsync are listed as Vulnerable; when installed they remain pending.
UNKNOWN for Ubuntu 20.04. No unqualified/cross-release binary is installed. The cumulative script keeps this requirement pending rather than reporting a false global PASS.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 20.04/Focal zlib, separately from Ubuntu 24.04/Noble.
어플라이언스 재부팅
No Focal patch is installed by this release.
서비스 중단
Vendor assessment pending. Noble fixed version does not establish Focal coverage.
Check the official CVE release status. Keep the installed Focal package and await a qualified cumulative revision; do not mix Ubuntu releases.
완료 확인: UNKNOWN / Needs evaluation for Focal as of26October2026.
Qualification covers the documented baselines and component checks. It does not demonstrate installation on every customer appliance or SMS/email delivery. Focal zlib coverage remains pending.
IMPORTANT — Update the PHP runtime serving your FoxBox web interface. CVE-2026-109618 and CVE-2026-109619 can allow unauthenticated remote code execution. Both advisories are rated Critical, CVSS v4.0 9.2. Select the correction for your actual distribution and PHP branch.
Memory corruption when request handling runs out of memory can lead to remote code execution. PHP identifies Apache mod_php as the highest-risk deployment.
Update the installed PHP 7.4 runtime and extensions using the official Ubuntu 20.04 backport, then restart and verify Apache. For upstream PHP 8.2/8.3/8.4/8.5 use 8.2.35/8.3.36/8.4.27/8.5.12 or later corrected releases; distribution versions differ.
보고서 날짜 기준 절차 및 재부팅 요구 사항
FoxBox customer appliances: Ubuntu 20.04 amd64, Apache mod_php7.4/prefork and PHP 7.4 CLI from Ubuntu packages. Run where PHP is installed, inside the application container when applicable. Installed extensions are detected automatically. FPM/embed, PPA/custom binary builds and other platforms require separate qualification.
어플라이언스 재부팅
Not required. The program never reboots the appliance. Any previously pending kernel reboot is separate.
서비스 중단
Brief web interruption: full stop/start of Apache through its service manager, with old-process exit and current PHP module checks. Other services are preserved.
Download the PHP 7.4 update ZIP below. It includes the automatic updater and original corrected packages; no UbuntuPro credentials are required on the appliance. Compare the complete SHA256 with this page.
sha256sum foxbox-php74-update-2026.10.22-r1.zip
Extract in a new private directory outside the webroot and verify every included file. Run inside the application environment as root.
Run the read-only compatibility check. The tool detects installed PHP 7.4 source packages, verifies packaged files and preserves absent optional extensions and newer revisions. Read README-EN.txt.
python3 foxbox_php74.py check
Arrange a maintenance window, a second administrative session, external backup and console/recovery access. Root, Python 3.8+, APT/dpkg, full perl and 512 MiB free are required. Unknown/custom runtimes, holds or unrelated dependencies stop the operation.
Apply the update. It first creates private recovery packages from this appliance, saves configuration/runtime hashes, and simulates an offline plan. It installs only existing PHP components, preserves local configuration and fully stops/starts only Apache. No host reboot or real messages.
python3 foxbox_php74.py apply --recovery-ready
Check the result, web login and read-only DB connection. PHP may still display7.4.3: the full package revision must be7.4.3-4ubuntu2.29+esm5. No real SMS/email delivery test.
If cli_restart_required is true, existing CLI daemons still hold old PHP in memory. Use the controlled service restart procedure for your application version, preserving queues/data, then repeat check. The updater reports this action and never terminates SMS daemons blindly.
Emergency recovery only: rollback compares the current state with the recorded post-install state, then restores the original packages saved from this appliance. It blocks on drift and preserves current business data. Rollback reintroduces the CVEs. Keep the private checkpoint out of the webroot.
python3 foxbox_php74.py rollback
완료 확인: Success requires corrected full package revisions, a refreshed web runtime and preserved configuration/extensions. Check the login page and read-only DB connectivity. Already current returns already_up_to_date without reinstalling or restarting. On a partial APT failure, preserve the private checkpoint and follow README recovery before retrying. Check cli_restart_required: false means no old CLI runtime was observed.
Internal request state may outlive freed memory and be reused by a later request in the same worker, with possible remote code execution.
Update the installed PHP 7.4 runtime and extensions using the official Ubuntu 20.04 backport, then restart and verify Apache. For upstream PHP 8.2/8.3/8.4/8.5 use 8.2.35/8.3.36/8.4.27/8.5.12 or later corrected releases; distribution versions differ.
보고서 날짜 기준 절차 및 재부팅 요구 사항
FoxBox customer appliances: Ubuntu 20.04 amd64, Apache mod_php7.4/prefork and PHP 7.4 CLI from Ubuntu packages. Run where PHP is installed, inside the application container when applicable. Installed extensions are detected automatically. FPM/embed, PPA/custom binary builds and other platforms require separate qualification.
어플라이언스 재부팅
Not required. The program never reboots the appliance. Any previously pending kernel reboot is separate.
서비스 중단
Brief web interruption: full stop/start of Apache through its service manager, with old-process exit and current PHP module checks. Other services are preserved.
Download the PHP 7.4 update ZIP below. It includes the automatic updater and original corrected packages; no UbuntuPro credentials are required on the appliance. Compare the complete SHA256 with this page.
sha256sum foxbox-php74-update-2026.10.22-r1.zip
Extract in a new private directory outside the webroot and verify every included file. Run inside the application environment as root.
Run the read-only compatibility check. The tool detects installed PHP 7.4 source packages, verifies packaged files and preserves absent optional extensions and newer revisions. Read README-EN.txt.
python3 foxbox_php74.py check
Arrange a maintenance window, a second administrative session, external backup and console/recovery access. Root, Python 3.8+, APT/dpkg, full perl and 512 MiB free are required. Unknown/custom runtimes, holds or unrelated dependencies stop the operation.
Apply the update. It first creates private recovery packages from this appliance, saves configuration/runtime hashes, and simulates an offline plan. It installs only existing PHP components, preserves local configuration and fully stops/starts only Apache. No host reboot or real messages.
python3 foxbox_php74.py apply --recovery-ready
Check the result, web login and read-only DB connection. PHP may still display7.4.3: the full package revision must be7.4.3-4ubuntu2.29+esm5. No real SMS/email delivery test.
If cli_restart_required is true, existing CLI daemons still hold old PHP in memory. Use the controlled service restart procedure for your application version, preserving queues/data, then repeat check. The updater reports this action and never terminates SMS daemons blindly.
Emergency recovery only: rollback compares the current state with the recorded post-install state, then restores the original packages saved from this appliance. It blocks on drift and preserves current business data. Rollback reintroduces the CVEs. Keep the private checkpoint out of the webroot.
python3 foxbox_php74.py rollback
완료 확인: Success requires corrected full package revisions, a refreshed web runtime and preserved configuration/extensions. Check the login page and read-only DB connectivity. Already current returns already_up_to_date without reinstalling or restarting. On a partial APT failure, preserve the private checkpoint and follow README recovery before retrying. Check cli_restart_required: false means no old CLI runtime was observed.
Automatic customer update for the Ubuntu 20.04 amd64 Apache/PHP 7.4 appliance baseline. Uses installed-package detection and private appliance-specific recovery; custom application changes still require compatibility review. This emergency correction does not restore general upstream PHP 7.4 support. The Ubuntu 24.04 host update remains a separate download.
IMPORTANT — Update the PHP runtime serving your FoxBox web interface. CVE-2026-109618 and CVE-2026-109619 can allow unauthenticated remote code execution. Both advisories are rated Critical, CVSS v4.0 9.2. Select the correction for your actual distribution and PHP branch.
Memory corruption when request handling runs out of memory can lead to remote code execution. PHP identifies Apache mod_php as the highest-risk deployment.
Update the installed PHP 7.4 runtime and extensions using the official Ubuntu 20.04 backport, then restart and verify Apache. For upstream PHP 8.2/8.3/8.4/8.5 use 8.2.35/8.3.36/8.4.27/8.5.12 or later corrected releases; distribution versions differ.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 20.04 amd64 application container, Apache mod_php 7.4 and installed matching extensions. Obtain packages through authorised Ubuntu Pro/ESM access. Different distributions, PHP branches and appliance versions need separate qualification.
어플라이언스 재부팅
Not required for this PHP update. Any previously pending kernel reboot is separate.
서비스 중단
Apache must restart so all workers load the corrected PHP runtime. A short web interruption is possible; CLI processes that stay running must also be refreshed.
Identify the application container, OS, architecture, web SAPI and installed PHP extensions. This procedure is for Ubuntu 20.04 amd64 with Apache mod_php 7.4. Do not run the Ubuntu 24.04 host patch inside this container.
Arrange a maintenance window and recovery access. Save PHP/Apache configuration, runtime hashes and the exact original packages in a private directory outside the webroot. Verify package restoration on an isolated container without production data, modems, queues or outgoing transports. Do not restore a database or SMS spool to roll back PHP.
Obtain the official Ubuntu Pro/ESM packages for the matching baseline using your authorised subscription. Ubuntu 20.04 requires php7.4 source-package revision 7.4.3-4ubuntu2.29+esm5 or later with both CVEs fixed. Keep credentials private. If the signed repository does not offer the correction, stop and contact support; a successful upgrade of the old public repository is not proof of remediation.
Build the list from installed PHP 7.4 runtime packages only; absent optional extensions must remain absent. Check signed APT origins and SHA-256 for every package. Simulate the exact local package set before installation. Reject removals, new packages, branch changes, unsatisfied dependencies or unrelated upgrades.
# Run from the private directory containing ONLY the reviewed .deb files.
sha256sum -c SHA256SUMS
apt-get --simulate --no-remove --no-install-recommends install ./*.deb
After the isolated update and rollback tests pass, reread live package/configuration hashes and review the live APT plan. Apply only the approved local packages. Preserve existing configuration; stop on unexpected prompts. Package scripts may restart Apache, so coordinate service interruption and never restart the entire appliance automatically.
After Syntax OK, refresh Apache in the maintenance window and confirm that every old worker has exited. Verify the web SAPI as well as CLI, the exact Debian package revisions, loaded extensions, login page and read-only database connectivity. Delete any temporary local-only diagnostic endpoint immediately. Do not send a real SMS or email as a check.
If checks fail, compare current hashes with the recorded post-update manifest. Only if they match, restore the saved original PHP packages with the reviewed downgrade plan and original configuration, then restart Apache and repeat checks. Stop on editor or package drift; preserve all current business data. A rollback reintroduces these vulnerabilities and is an emergency recovery step.
완료 확인: The correction is established by the vendor package revision and refreshed web workers, not by the visible PHP 7.4.3 number alone. Test the supported appliance workflow without real message delivery. The host cumulative ZIP below does not update application containers.
Internal request state may outlive freed memory and be reused by a later request in the same worker, with possible remote code execution.
Update the installed PHP 7.4 runtime and extensions using the official Ubuntu 20.04 backport, then restart and verify Apache. For upstream PHP 8.2/8.3/8.4/8.5 use 8.2.35/8.3.36/8.4.27/8.5.12 or later corrected releases; distribution versions differ.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 20.04 amd64 application container, Apache mod_php 7.4 and installed matching extensions. Obtain packages through authorised Ubuntu Pro/ESM access. Different distributions, PHP branches and appliance versions need separate qualification.
어플라이언스 재부팅
Not required for this PHP update. Any previously pending kernel reboot is separate.
서비스 중단
Apache must restart so all workers load the corrected PHP runtime. A short web interruption is possible; CLI processes that stay running must also be refreshed.
Identify the application container, OS, architecture, web SAPI and installed PHP extensions. This procedure is for Ubuntu 20.04 amd64 with Apache mod_php 7.4. Do not run the Ubuntu 24.04 host patch inside this container.
Arrange a maintenance window and recovery access. Save PHP/Apache configuration, runtime hashes and the exact original packages in a private directory outside the webroot. Verify package restoration on an isolated container without production data, modems, queues or outgoing transports. Do not restore a database or SMS spool to roll back PHP.
Obtain the official Ubuntu Pro/ESM packages for the matching baseline using your authorised subscription. Ubuntu 20.04 requires php7.4 source-package revision 7.4.3-4ubuntu2.29+esm5 or later with both CVEs fixed. Keep credentials private. If the signed repository does not offer the correction, stop and contact support; a successful upgrade of the old public repository is not proof of remediation.
Build the list from installed PHP 7.4 runtime packages only; absent optional extensions must remain absent. Check signed APT origins and SHA-256 for every package. Simulate the exact local package set before installation. Reject removals, new packages, branch changes, unsatisfied dependencies or unrelated upgrades.
# Run from the private directory containing ONLY the reviewed .deb files.
sha256sum -c SHA256SUMS
apt-get --simulate --no-remove --no-install-recommends install ./*.deb
After the isolated update and rollback tests pass, reread live package/configuration hashes and review the live APT plan. Apply only the approved local packages. Preserve existing configuration; stop on unexpected prompts. Package scripts may restart Apache, so coordinate service interruption and never restart the entire appliance automatically.
After Syntax OK, refresh Apache in the maintenance window and confirm that every old worker has exited. Verify the web SAPI as well as CLI, the exact Debian package revisions, loaded extensions, login page and read-only database connectivity. Delete any temporary local-only diagnostic endpoint immediately. Do not send a real SMS or email as a check.
If checks fail, compare current hashes with the recorded post-update manifest. Only if they match, restore the saved original PHP packages with the reviewed downgrade plan and original configuration, then restart Apache and repeat checks. Stop on editor or package drift; preserve all current business data. A rollback reintroduces these vulnerabilities and is an emergency recovery step.
완료 확인: The correction is established by the vendor package revision and refreshed web workers, not by the visible PHP 7.4.3 number alone. Test the supported appliance workflow without real message delivery. The host cumulative ZIP below does not update application containers.
Vendor security backports can retain the PHP 7.4.3 base version: check the full package revision. PHP 8.1 and older are outside upstream support; this emergency correction does not restore general upstream support. The existing Ubuntu 24.04 host patch remains available separately and does not patch PHP inside containers.
공식 출처
보안 업데이트 노트 — 2026년 10월보고서를 읽으십시오. +
최초 게시 위치: 19 October 2026
10월 12일~18일 주간 검토에서 도출된 보안 우선순위(10월 19일 공식 자료 확인). 해당 운영 체제 및 구성 요소에 맞는 업데이트 절차를 선택하십시오.
소스 주간 검토: 18 October 2026
P1 · Ubuntu 24.04 / OpenSSH1:9.6p1-3ubuntu13.20
Canonical은 10월 14일에 9개의 취약점에 대한 수정 사항을 발표했습니다. 이 권고 사항은 Ubuntu 24.04 OpenSSH 클라이언트 및 서버 패키지에 적용됩니다.
설치된 Ubuntu 24.04 SSH 패키지를 수정된 버전 이상으로 업데이트한 다음, 새로운 관리자 연결이 제대로 되는지 확인합니다.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 24.04 호스트 패키지만 해당됩니다. 기존의 승인된 관리자 계정을 사용하고 현재 SSH 구성을 유지하며 복구 경로를 사용할 수 있도록 두 개의 독립적인 SSH 세션을 열어 두십시오. 설치된 패키지와 활성 서비스가 이미 목표를 충족하는 경우 재설치가 필요하지 않습니다.
어플라이언스 재부팅
일반적으로 OpenSSH 패키지 업데이트 자체에는 필요하지 않습니다.
서비스 중단
업데이트 중에 SSH가 다시 시작될 수 있습니다. 기존 세션은 보장된 복구 채널이 아니므로 세션을 닫기 전에 새 연결을 확인하십시오.
이것이 애플리케이션 컨테이너가 아닌 Ubuntu 24.04 호스트인지 확인하십시오. 설치된 SSH 패키지를 확인하십시오. 운영 체제 기준선이 다르면 중지하십시오.
각 패키지의 설치 상태 및 최소 버전을 확인하십시오. REPAIR REQUIRED 또는 UPDATE REQUIRED에서 중지하십시오. 누락된 패키지는 보고되고 누락된 상태로 유지됩니다. 그런 다음 일반 관리 경로를 통해 별도의 새 SSH 연결을 열고 구성된 키 제한 및 포워딩을 테스트하십시오.
for package in openssh-client openssh-server openssh-sftp-server; do
state=$(dpkg-query -W -f='${db:Status-Abbrev}' "$package") || {
printf '%s: NOT INSTALLED\n' "$package"; continue;
}
case "$state" in
'ii '|'hi ') ;;
*) printf '%s: REPAIR REQUIRED (%s)\n' "$package" "$state"; continue ;;
esac
version=$(dpkg-query -W -f='${Version}' "$package") || continue
if dpkg --compare-versions "$version" ge '1:9.6p1-3ubuntu13.20'; then
printf '%s: OK (%s)\n' "$package" "$version"
else
printf '%s: UPDATE REQUIRED (%s)\n' "$package" "$version"
fi
done
완료 확인: 버전 확인 및 새로 작동하는 SSH 연결이 통과해야 합니다. 설치된 패키지 버전만으로는 실행 중인 서비스가 새로 고쳐졌음을 입증할 수 없습니다. 다른 시스템 업데이트로 인해 요청된 재부팅은 별도로 처리해야 합니다.
P1 · Ubuntu 24.04 / Kernel6.8.0-147.147
10월 13일 업데이트로 커널 ABI가 변경되었습니다. Canonical은 재부팅 및 호환 가능한 타사 모듈을 요구합니다.
적용 가능한 DKMS 모듈, 모뎀 드라이버 및 복구 경로를 확인한 후 커널 변경 및 제어된 재부팅 계획 수립. 설치된 커널은 해당 버전으로 성공적으로 부팅된 후에만 활성화됩니다.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 24.04 GA 일반 커널 6.8.0-147.147. 설치와 재부팅은 별개의 단계입니다. 실제 하드웨어 및 복구 요구 사항에 맞춰 두 단계를 모두 예약하십시오.
어플라이언스 재부팅
예. 설치된 새 커널을 활성화하려면 필요합니다. 유지 관리 기간을 예약하세요.
서비스 중단
호스트 재부팅으로 어플라이언스 서비스가 중단됩니다. DKMS, 타사 드라이버 및 모뎀 호환성을 먼저 검증해야 합니다.
설치 또는 재부팅 전에 부팅 복구, 이전 부팅 가능한 커널 및 해당 DKMS/타사 모듈(bl_noah 포함)을 확인하십시오. dkms 명령이 없다고 해서 호환성이 입증되는 것은 아닙니다.
해당 하드웨어에서 모듈 빌드 및 로드, 모뎀 감지, QMI/직렬 인터페이스, 네트워크 및 페일오버를 확인합니다. 누적 패치는 트리에 포함된 모듈이 있는 일반 GA 6.8 커널을 지원합니다. 감지된 DKMS 또는 외부 모듈의 경우 커널을 변경하기 전에 어플라이언스별 절차를 수행해야 합니다.
사전 요구 사항 검사 및 복구 경로가 준비된 후에만 제어된 재부팅을 예약합니다. 재부팅 후 실행 중인 커널과 어플라이언스 상태를 다시 확인합니다. 재부팅을 연기하면 커널 활성화가 보류 상태로 남습니다.
uname -r
완료 확인: 커널 6.8.0-147-generic 또는 이후 호환되는 GA 6.8 generic 버전이 실행 중이어야 하며, 부팅 후 해당 모듈, 모뎀 경로 및 서비스가 확인되어야 합니다.
P1 · MySQL 8.4
Oracle은 2026년 10월 20일자 중요 패치 업데이트를 발표했습니다. 사전 릴리스에는 MySQL Server 8.4.0~8.4.11이 영향을 받는 릴리스 목록에 포함되어 있으며, 최종 업데이트 대상은 아직 확정되지 않았습니다.
기존 8.4.12 Docker 보안 업데이트는 백업, 복원 및 데이터베이스 호환성을 포함하여 별도로 평가 중입니다. 10월 CPU 목표는 최종 권고안 및 이미지 검증 후 선정됩니다.
보고서 날짜 기준 절차 및 재부팅 요구 사항
이미 제공된 8.4.12 업데이트는 MySQL Docker 이미지에 특화되어 있습니다. 이는 최종 목표가 아직 미정인 10월 CPU와는 별개입니다. 테스트된 이미지 소스와 정확한 다이제스트가 필요합니다.
어플라이언스 재부팅
이미지 업데이트 자체에 대한 호스트 재부팅이 필요하지 않습니다.
서비스 중단
예: 교체 데이터베이스 이미지를 적용하려면 데이터베이스/컨테이너를 재시작하고 유지 관리 기간을 예약해야 합니다.
자격 증명이나 고객 데이터를 내보내지 않고 배포된 MySQL 버전, 이미지 소스, 다이제스트, 볼륨 및 복제 경로를 식별합니다. 모든 레지스트리에 동일한 태그가 존재한다고 가정하지 마십시오.
8.4.12 버전의 경우, 대표 테스트 데이터에서 검증된 이미지를 확인하십시오. 시작, 스키마 호환성, 재시작, 백업/복원 및 MySQL-ClickHouse 연속성을 확인하십시오.
유지 관리 기간에 어플라이언스별 업그레이드 및 복구 절차를 사용합니다. 이전에 고정된 이미지와 검증된 백업을 유지합니다. 컨테이너만 복원하는 경우 데이터베이스 형식 변경을 되돌릴 수 없습니다.
10월 20일 CPU의 경우, 최종 권고 사항에 명시된 대상 버전과 이미지를 사용하십시오. 해당 업데이트 지침은 다음 날짜의 릴리스에 포함될 예정입니다.
완료 확인: 서비스 재시작 후 데이터베이스 상태, 애플리케이션 액세스 및 해당 복제/수집 경로를 확인합니다.
Canonical은 10월 14일에 curl/libcurl 및 python3-urllib3에 대한 새로운 보안 수정 사항을 발표했습니다.
설치된 Ubuntu 호스트 패키지와 해당 종속성이 누적 요구 사항을 충족하는지 확인하십시오. 호스트 APT 업데이트는 컨테이너 내부의 pip 패키지 또는 라이브러리를 업데이트하지 않습니다.
보고서 날짜 기준 절차 및 재부팅 요구 사항
Ubuntu 24.04 호스트 APT 패키지만 해당됩니다. 컨테이너 라이브러리 및 pip 설치는 별도입니다. 동일한 소스 패키지 제품군의 해당 설치된 바이너리를 포함하십시오.
어플라이언스 재부팅
일반적으로 이러한 라이브러리만으로는 필요하지 않습니다.
서비스 중단
영향을 받는 애플리케이션/서비스를 재시작하여 업데이트된 라이브러리를 로드하십시오.
설치된 curl/libcurl 및 python3-urllib3 패키지가 필요한 버전보다 낮은지 확인하기 위해 누적 패치를 검사 모드로 실행합니다. 이 호스트에서 사용하지 않는 패키지는 건너뜁니다.
APT 인덱스를 새로 고치고, 설치된 패키지와 종속성을 확인하기 위해 범위가 지정된 --simulate --only-upgrade --no-remove 트랜잭션을 검토합니다. 올바른 Ubuntu 버전은 curl/libcurl >= 8.5.0-2ubuntu10.16 및 python3-urllib3 >= 2.0.7-1ubuntu0.8입니다.
유지 관리 기간에 누적 패치를 적용한 다음 영향을 받는 애플리케이션을 다시 시작하고 관련 HTTPS, 프록시 및 Python 경로를 확인합니다.
완료 확인: 누적 검사기를 다시 실행하고 영향을 받는 실행 중인 서비스가 업데이트된 라이브러리를 사용하는지 확인합니다.
P2 · ClickHouse26.8.30.8 LTS
공식 26.8 LTS 패치는 10월 17일에 게시되었습니다. 이 릴리스만으로 모든 FoxBox 설치에 대한 긴급 보안 요구 사항이 발생하는 것은 아닙니다.
후보를 승격하기 전에 수집, SMS/DLR 통계, 보존, 재시작 및 복구를 검증합니다. 자동 데이터베이스 또는 컨테이너 업데이트는 포함되지 않습니다.
보고서 날짜 기준 절차 및 재부팅 요구 사항
26.8 LTS 라인에 대한 실험실 검증 후보입니다. 검증이 성공할 때까지 현재 배포된 버전이 고정됩니다.
어플라이언스 재부팅
이 데이터베이스 업데이트 자체에 대한 호스트 재부팅이 필요하지 않습니다.
서비스 중단
적격 업데이트를 적용할 때 서비스/컨테이너를 다시 시작해야 합니다.
일회용 연구실 인스턴스를 준비하고 정확한 26.8.30.8 LTS 패키지 또는 이미지를 고정합니다. 배포된 프로덕션 버전을 보존합니다.
합성 SMS/DLR 수집, MergeTree 쿼리, TTL/보존, 재시작 및 복구를 테스트합니다. 어플라이언스에서 사용하는 MySQL 통합을 검증합니다.
호환성이 확인되면 백업, 서비스 중단 시간 및 복구 검사를 포함하여 어플라이언스별 업그레이드 절차를 사용합니다. 이 후보는 호스트 패치와 별개입니다.
완료 확인: 승인 전에 모든 관련 데이터 수집, 조회, 보존 및 복구 테스트를 통과해야 합니다.
P2 · Cloudflare Tunnelcloudflared 2026.10.1
Cloudflare는 10월 15일에 cloudflared 2026.10.1을 게시했습니다. 이는 호환성 검증 후보입니다.
배포 전 HTTPS 및 SSH 액세스, 재연결 및 FoxBox API 경로 테스트 릴리스 번호만으로는 긴급 업그레이드를 추론할 수 없습니다.
보고서 날짜 기준 절차 및 재부팅 요구 사항
호환성 후보는 cloudflared 2026.10.1입니다. 바이너리를 선택하기 전에 설치된 아키텍처와 패키지 소스를 확인하십시오.
어플라이언스 재부팅
이 서비스 업데이트 자체에 대한 호스트 재부팅이 필요하지 않습니다.
서비스 중단
Cloudflared를 재시작하면 터널이 중단됩니다. 교체 전에 독립적인 복구 액세스가 필요합니다.
설치된 버전을 읽으십시오. SSH 액세스를 제공하는 터널을 변경하기 전에 대체 관리 경로를 준비하십시오.
cloudflared --version
먼저 연구실 호스트에서 공식 2026.10.1 빌드 및 체크섬을 검증합니다. HTTPS/SSH, 서비스 재시작, WAN 재연결, 후행 슬래시 및 인코딩된 FoxBox API 경로 테스트
호환성 검사 후 어플라이언스의 확인된 설치 방법을 사용하고 고정된 복구 버전을 유지합니다. 이 후보는 호스트 패치와 별개입니다.
완료 확인: 서비스 재시작 후 새로운 HTTPS 및 SSH 연결을 확인하고 터널이 안정화될 때까지 복구 액세스를 유지하십시오.
누적 패치는 Ubuntu 24.04 호스트 패키지를 업데이트합니다. 데이터베이스 및 컨테이너 업데이트와 아래의 재시작 요구 사항에 대한 구성 요소 지침을 따르십시오.