Yeastar distribution in Australia by TeraFiBuilt for Australian resellers
TeraFi and Yeastar
Book a demo

Category: News

  • Yeastar Security Advisory: Upgrade P-Series to V26.1 GA Now

    Yeastar Security Advisory: Upgrade P-Series to V26.1 GA Now

    Yeastar has issued a critical security advisory for the P-Series: upgrade every P-Series PBX to V26.1 GA as soon as possible.

    Attackers are running automated scans across public IP ranges and common ports to find exposed PBXs. Once they find one, they are getting past standard validation and logging in to the PBX Management Portal. From there, they place unauthorised outbound calls – classic toll fraud that can run up a large bill in hours and knock out normal calling.

    If you manage P-Series systems for customers, treat this as a this-week job, not a next-maintenance-window job.

    Risk level: Critical

    Who is affected

    All three P-Series editions are in scope: Software Edition (PSE), Appliance Edition (PAE) and Cloud Edition (PCE). S-Series PBXs are not affected and need no action.

    Prioritise these deployments first:

    • PSE instances on public cloud with a public IP assigned directly to the server
    • Any public cloud deployment without tight firewall rules
    • Systems where Management Portal logins use extension numbers as usernames

    How to upgrade to V26.1 GA

    Target firmware: XX.25.0.23 for PAE/PSE and XX.25.0.25 for PCE. This release carries Yeastar’s security hardening against these attacks.

    Single PBX

    1. Online: log in to the PBX Management Portal, go to Maintenance > Upgrade, select V26.1 GA and click Upgrade Now.
    2. Offline: download V26.1 GA from the Yeastar firmware page and upload it to the PBX.

    Fleet (batch) upgrades

    • PCE: schedule batch upgrades from the Task module in Yeastar Central Management (YCM).
    • PAE/PSE: run batch upgrades through Yeastar Remote Management Premium (RMP) linked to YCM.

    No RMP access and a fleet to get through? Contact us and we’ll help you sort batch access.

    Don’t stop at the firmware

    The upgrade closes the current hole. Good hygiene stops the next one. While you’re in each system:

    • Remove port forwards to the PBX and block unknown IPs – only trusted networks should reach the Management Portal
    • Enforce strong, unique passwords and stop using extension numbers as portal usernames
    • Tighten extension login permissions to what each user actually needs
    • Restrict outbound calling – block international and premium destinations unless a customer needs them, and set call limits
    • Check recent CDRs for unexpected international or after-hours calls

    Yeastar’s VoIP security best practices guide covers each of these in detail.

    Need a hand?

    Yeastar Australia is here to help partners get through this quickly – whether it’s a single upgrade that won’t take, batch access for your fleet, or a second set of eyes on a system you think has been hit.

    Contact the Yeastar Australia team and we’ll get you sorted.

    Source: Yeastar Security Advisory, 3 November 2026