what is the Amazon Neptune Security Update in 2026. Amazon Neptune Vulnerability: How to Fix CVE-2026-110812
AWSAWS Supportaws support services

Amazon Neptune Vulnerability: How to Fix CVE-2026-110812

by Tanisha Mathew
written by Tanisha Mathew

Ask most people what database security means, and they’ll say passwords and access rules. Fair enough, but it’s only half of it. You can lock down logins perfectly and still be exposed if the engine underneath is running a vulnerable version. On October 15, 2026, AWS published a notice about CVE-2026-110812, an Amazon Neptune Gremlin vulnerability. AWS has released patched engine versions and recommends that affected customers upgrade. The CVE-2026-110812 fix is available in Neptune engine versions 1.4.7.1, 1.4.8.1, and 1.5.0.0. If you’re running Neptune, check your engine version and review who can send queries to your clusters. You can find the details in the official AWS security bulletin. What Is the Amazon Neptune Gremlin Vulnerability? Neptune is Amazon’s managed …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
CVE-2026-98432: What Linux Server Administrators Must Check About the Critical TCP Flaw
Miscellaneous

CVE-2026-98432: How to Check and Fix the Critical Linux TCP Vulnerability

by Tanisha Mathew
written by Tanisha Mathew

A critical vulnerability, CVE-2026-98432, has emerged within the IPv4 TCP networking stack of the Linux kernel, prompting urgent attention from hosting providers, system administrators, and DevOps professionals. Rated with a CVSS score of 9.8, this critical Linux kernel vulnerability stems from a use-after-free condition. An unauthenticated remote attacker can potentially trigger kernel memory corruption, resulting in a complete system crash or, under certain conditions, remote code execution (RCE). The critical concern is that this Linux TCP vulnerability extends beyond individual Linux distributions or specific applications, as it resides within the fundamental code responsible for IPv4 TCP connection handling. Consequently, any server running an affected kernel build may remain exposed, regardless of the hosting control panel or applications installed. For administrators …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
SupportPro CEO joins Global leaders at CloudFest Americas 2026 
CloudCloud Support Servicesweb hostingweb hosting support

SupportPro CEO joins Global leaders at CloudFest Americas 2026 

by Tanisha Mathew
written by Tanisha Mathew

If your 2027 plans depend on partnerships you haven’t built yet, November is the right time to start building them. In the hosting and cloud industry, most partnerships start with a conversation, not a contact form. A well-timed meeting at an industry event can open doors that months of emails rarely do. That’s the opportunity at CloudFest Americas 2026, and we’re pleased to share that the SupportPro team will be attending. In this guide, we cover what’s happening in Miami, who the event is for, and what you can gain from attending. What is CloudFest Americas 2026? CloudFest Americas 2026 is a two-day internet infrastructure festival on November 11-12, 2026, at Ice Palace Studios in Miami, Florida. It brings together …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
PHP2Shell: What Hosting Administrators Must Check Now
cPanelSecurityServer MonitoringServer Securityweb hostingweb hosting supportWordPress

PHP2Shell: What cPanel, Plesk, DirectAdmin, and CWP Administrators Must Check Now?

by Tanisha Mathew
written by Tanisha Mathew

PHP security updates should be a priority for hosting administrators after the disclosure of two critical vulnerabilities known as PHP2Shell. Tracked as CVE-2026-109618 and CVE-2026-109619, these vulnerabilities affect PHP’s core runtime and can allow unauthenticated attackers to execute code remotely on vulnerable servers. Both vulnerabilities carry a CVSS v4.0 score of 9.2. Security authorities have also reported exploitation in the wild, making this an issue that requires immediate attention. For hosting providers, updating a single PHP installation is not enough. A server may have several PHP versions installed, with different websites using different handlers and configurations. First, identify every PHP runtime serving web requests, verify its security status, and apply the appropriate vendor updates. This includes PHP-FPM, Apache mod_php, CGI, …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
Amazon Linux 2 EFS Utilities Security Update: What Administrators Should Check Introduction Keeping Linux systems secure requires more than applying updates to the operating system kernel. Utilities that support storage, networking, and cloud service integrations also need regular security reviews. For administrators running Amazon Linux 2 workloads with Amazon Elastic File System (Amazon EFS), a newly published security advisory highlights the importance of checking these supporting packages. On October 28, 2026, Amazon Web Services (AWS) released security advisory ALAS2-2026-4044, addressing CVE-2026-15957 in the amazon-efs-utils package. AWS classifies the advisory as Important and identifies amazon-efs-utils-3.1.3-1.amzn2 as the corrected package. The underlying vulnerability involves uncontrolled recursion in Smithy-RS-generated deserialization functions, which can exhaust the stack and cause a process to abort. For Linux administrators, hosting providers, managed service providers (MSPs), and DevOps teams, the immediate priority is to identify affected hosts, apply the available security update, and confirm that EFS-dependent workloads continue to operate correctly. What Is the Amazon Linux 2 EFS Utilities Security Update? The amazon-efs-utils package provides utilities that help Linux instances connect to and use Amazon EFS. These utilities support EFS mount operations and related functionality used by applications that depend on shared file storage. AWS published ALAS2-2026-4044 to address a vulnerability affecting this package on Amazon Linux 2. The advisory identifies the following details: Security advisory: ALAS2-2026-4044 Release date: October 28, 2026 Affected package: amazon-efs-utils Vulnerability: CVE-2026-15957 AWS severity: Important Corrected package: amazon-efs-utils-3.1.3-1.amzn2 The corrected package is available for both x86_64 and ARM64 (aarch64) architectures. Administrators can review the official AWS Amazon Linux 2 security advisory for the complete package and remediation details. Understanding CVE-2026-15957 and Its Potential Impact CVE-2026-15957 concerns uncontrolled recursion in deserialization functions generated by the Smithy-RS code generation framework. Smithy-RS is used to generate Rust-based HTTP clients and servers, including components that support the AWS SDK for Rust. The affected deserialization functions handle JSON, CBOR, and XML data. When these functions process deeply nested data associated with a recursive model, uncontrolled recursion can consume excessive stack space. In a vulnerable, reachable component, an attacker may be able to trigger stack exhaustion and cause the affected process to abort. This is primarily a denial-of-service (DoS) risk, rather than a vulnerability that directly implies data theft or unauthorized modification. For infrastructure teams, the operational concern is that a process failure can interrupt a service that depends on the affected component. The actual impact depends on how the vulnerable functionality is exposed and used within the environment. The advisory identifies amazon-efs-utils as the affected Amazon Linux 2 package. However, administrators should not assume that every EFS mount is directly exploitable or that an existing mount will necessarily fail because of this vulnerability. Instead, they should prioritize the package update and verify the availability of applications and services that rely on EFS. Tenable also provides a Nessus plugin for ALAS2-2026-4044, which identifies systems running an affected package version. Its scanner classification differs from AWS's advisory severity, so teams should follow their organization's vulnerability assessment and prioritization procedures. How to Identify Affected Amazon Linux 2 Hosts The first step is to determine which instances have the affected package installed and whether they have received the corrected version. 1. Check the installed package version Connect to the Amazon Linux 2 instance and run: rpm -q amazon-efs-utils Review the output and compare the installed version with the corrected release, 3.1.3-1.amzn2. Versions earlier than the corrected release are identified as affected by the advisory. For environments with multiple instances, use configuration management, inventory tools, or vulnerability scanners to identify affected hosts across the fleet. 2. Review the advisory-specific update Check whether the security update is available through the configured package repositories: sudo yum updateinfo info ALAS2-2026-4044 Repository metadata and available update information can vary depending on the system's configuration. If the command does not return the expected information, review repository connectivity and metadata before concluding that the host is unaffected. 3. Prioritize EFS-dependent systems Pay particular attention to production servers that use EFS for shared application files, uploads, content directories, or other persistent data. Record the affected instances, their installed package versions, the applications using EFS, and the appropriate maintenance arrangements. This inventory helps teams coordinate remediation without overlooking workloads that are not frequently accessed or monitored. How to Apply the Security Update AWS provides two remediation options for Amazon Linux 2. To update only the EFS utilities package, run: sudo yum update amazon-efs-utils Alternatively, to apply the update associated with the specific security advisory, run: sudo yum update --advisory ALAS2-2026-4044 Choose the approach that fits your patch management policy. Updating the specific package may help limit the scope of a targeted maintenance operation, while advisory-based updates can be useful when tracking remediation against a particular security bulletin. Before making changes on production systems, review the package transaction and follow your organization's change management procedures. For managed hosting environments, consider staging the update on a representative instance before proceeding with a wider rollout. After installation, confirm the package version: rpm -q amazon-efs-utils Verify that the installed release matches the corrected package version or a later applicable fixed release. If the update fails, investigate repository availability, package dependencies, and any package management errors. Avoid assuming that an update was successful simply because the command was executed. What to Validate After Updating EFS Utilities Applying the patch is only part of the remediation process. Administrators should also verify that EFS-dependent applications continue to function as expected. Check EFS mount status. Review the mounted filesystems and confirm that the expected EFS mount points remain available: findmnt -t nfs4 Amazon EFS commonly uses NFSv4.1 for Linux mounts, so reviewing NFSv4 mount entries can help confirm that expected filesystems are present. Test application-level access. Verify that applications can read and write to their designated EFS directories using the appropriate service accounts and permissions. A successful mount alone does not guarantee that every application has the required access. Review system logs. Check relevant system and application logs for mount failures, permission errors, unexpected process exits, or other symptoms following the update. Monitor dependent workloads. For production systems, monitor application health, request failures, background jobs, and services that rely on shared EFS storage. Compare the results against the expected baseline and investigate any unexpected changes. Document remediation. Record the package version before and after the update, the affected hosts, the maintenance window, and the validation results. This information supports internal security reviews and compliance reporting. These checks help establish that the vulnerability has been addressed without introducing avoidable disruption to dependent services. Security Considerations for Amazon Linux 2 Environments Amazon Linux 2 is now an end-of-support (EOS) operating system, as identified in the AWS advisory. Organizations that continue to operate Amazon Linux 2 should therefore review both immediate security fixes and their longer-term operating system strategy. Applying available security updates remains important for systems that are still in use. However, individual package updates should not be treated as a substitute for evaluating the risks of continuing to run an EOS platform. Hosting providers and MSPs should maintain an accurate inventory of legacy instances, track applicable security advisories, and establish a migration plan for workloads that can move to a supported operating system. Migration planning should account for application compatibility, package availability, EFS integration, and operational dependencies. For DevOps teams, automated package inventory and vulnerability scanning can help identify outdated components before they become overlooked maintenance issues. A repeatable process for remediation and post-update validation also makes security response more consistent across environments. Conclusion The Amazon Linux 2 EFS utilities security update ALAS2-2026-4044 addresses CVE-2026-15957, a denial-of-service vulnerability involving uncontrolled deserialization recursion. AWS released the advisory on October 28, 2026, and identifies amazon-efs-utils-3.1.3-1.amzn2 as the corrected package. Administrators should check installed package versions, identify affected hosts, apply the appropriate update, and validate EFS mounts and dependent applications. Organizations running Amazon Linux 2 should also consider the operating system's end-of-support status when planning ongoing security maintenance. If your environment includes multiple Amazon Linux 2 instances, our team can assist with identifying affected hosts, coordinating the required updates, and validating EFS-dependent workloads to help minimize operational disruption.
AWSLinux

CVE-2026-15957: Is Your Amazon Linux 2 Server Affected?

by Tanisha Mathew
written by Tanisha Mathew

Linux administrators must keep more than the operating system kernel up to date. Supporting packages that handle storage, networking, and cloud integrations also need regular maintenance.On October 28, 2026, AWS released security advisory ALAS2-2026-4044 for CVE-2026-15957, a vulnerability affecting the amazon-efs-utils package on Amazon Linux 2. AWS classifies the advisory as Important and identifies amazon-efs-utils-3.1.3-1.amzn2 as the corrected package. The vulnerability involves uncontrolled recursion in Smithy-RS-generated deserialization functions. Deeply nested data can exhaust the stack and cause a process to abort, creating a denial-of-service (DoS) risk. Administrators should identify affected instances, update the package, and verify that applications using Amazon Elastic File System (EFS) continue to work. What Is the Amazon Linux 2 EFS Utilities Update? The amazon-efs-utils package provides …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
AGENTS.md Attack How Malicious Files Hijack AI Coding Agents
Artificial IntelligenceSecurity

AI Coding Agent Security: How Malicious AGENTS.md Files Can Hijack AI Workflows

by Tanisha Mathew
written by Tanisha Mathew

AI coding agents can do more than suggest code. Depending on their permissions, they can read project files, run terminal commands, install packages, change configuration, and call external services. That speed creates a new security boundary: AI coding agent security agents may act on instructions found in files that nobody has reviewed. As the AI coding agent plugin vulnerability CVE-2026-107322 showed earlier this month, the tooling around these agents is already a target. On October 22, 2026, security company Forever Security said it discovered a malicious AGENTS.md file in a customer’s Downloads folder. The researchers also reproduced attack chains involving OpenAI Codex and Claude Code during controlled testing. Their investigation showed how an ordinary-looking instruction file could potentially steer an …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
ZDI-CAN-33367 How Can Hosting Providers Assess Linux Server Exposure
dedicated server supportDedicated serversLinuxServer Security

Essential Guide for Hosting Providers to Assess Linux Server Exposure

by Tanisha Mathew
written by Tanisha Mathew

What Hosting Administrators Need to Know A Linux server can run websites smoothly and still have a serious flaw in its operating system. That’s why hosting providers need to pay attention to kernel vulnerabilities, even when their applications and customer accounts appear to work normally. One recent example is ZDI-CAN-33367, a Linux kernel vulnerability that allows a local, unprivileged user to change file contents stored in memory under specific conditions. The affected file may belong to another user or even root, although the attacker normally can read it but not modify it. The vulnerability can create a serious problem for hosting providers that run multiple customer accounts on the same server. If an attacker gains local access, they may use …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
Wiz Runtime Sensor GKE (Preview) A Readiness Guide for Kubernetes Teams
Miscellaneous

Wiz Runtime Sensor on GKE: Is Your Team Ready to Switch It On?

by Tanisha Mathew
written by Tanisha Mathew

Picture a new apartment building. Before anyone moves in, an inspector checks every lock and window. That’s image scanning. It tells you what could go wrong.. But what if someone is already jiggling a door handle at 2 a.m.? That’s where Kubernetes runtime security comes in. It’s the smoke alarm: it spots trouble while it’s happening. On 16 October 2026, Google announced a preview of the Wiz Runtime Sensor as a managed add-on for Google Kubernetes Engine (GKE). It covers both Standard and Autopilot clusters. The big idea: GKE installs and updates the sensor for you, instead of a Helm release you babysit across dozens of clusters. If you run Kubernetes for a SaaS product or manage clusters for clients, …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
CVE-2026-99999 (PwnEscape) Is Your KVM Host at Risk A Simple Patch Checklist
Dedicated tech supportLinuxSecurityServer Security

CVE-2026-99999: Is Your KVM Host at Risk? A Simple Patch Checklist

by Tanisha Mathew
written by Tanisha Mathew

Picture an apartment building. The building is your server. Each apartment is a virtual machine (VM) that you rent to a customer. Most tenants are lovely. A few are curious. And once in a while, one of them finds a way to walk through the wall into the building’s control room. That is the kind of problem CVE-2026-99999 creates. Researchers call it PwnEscape. It is a flaw in the Linux kernel, in the part that handles virtio-net and TAP networking. AWS published a bulletin about it (2026-137-AWS) on October 15, 2026, and advice from different vendors keeps changing as new details emerge. This checklist is for VPS providers, data centers, and businesses that run their own KVM hosts. By the …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
What Are CVE-2026-109618 and CVE-2026-109619
cPanelSecurityserver checkupserver managementweb hosting

PHP CVE-2026-109618 and CVE-2026-109619: What Hosting Teams Should Do Now?

by Tanisha Mathew
written by Tanisha Mathew

PHP CVE-2026-109618 and CVE-2026-109619 are critical remote code execution vulnerabilities disclosed on October 21, 2026. Both vulnerabilities could allow attackers to execute code on affected PHP servers without authentication. PHP has released patched versions, so hosting providers should identify vulnerable installations and apply the appropriate updates promptly. Updating WordPress, plugins, and themes alone does not protect a website from vulnerabilities in the underlying PHP runtime. If a server still runs a vulnerable PHP version, the website may remain at risk even when its applications are fully updated. For web hosting companies, fixing these vulnerabilities requires more than updating a single server. One server may run multiple PHP versions, several PHP-FPM pools, and hundreds of customer websites. Hosting environments may also …

Continue Reading
0 comments
0 FacebookTwitterPinterestEmail
Newer Posts
Older Posts