Skip to content

Menu
  • Home
Menu

CVE-2026-30240 – Budibase PWA ZIP Upload Path Traversal Allows Reading Arbitrary Server Files Including All Environment Secrets

Posted on March 10, 2026
CVE ID :CVE-2026-30240

Published : March 9, 2026, 9:16 p.m. | 1 hour, 57 minutes ago

Description :Budibase is a low code platform for creating internal tools, workflows, and admin panels. In 3.31.5 and earlier, a path traversal vulnerability in the PWA (Progressive Web App) ZIP processing endpoint (POST /api/pwa/process-zip) allows an authenticated user with builder privileges to read arbitrary files from the server filesystem, including /proc/1/environ which contains all environment variables — JWT secrets, database credentials, encryption keys, and API tokens. The server reads attacker-specified files via unsanitized path.join() with user-controlled input from icons.json inside the uploaded ZIP, then uploads the file contents to the object store (MinIO/S3) where they can be retrieved through signed URLs. This results in complete platform compromise as all cryptographic secrets and service credentials are exfiltrated in a single request.

Severity: 9.6 | CRITICAL

Visit the link for more details, such as CVSS details, affected products, timeline, and more…

🤖 AI-Generated Patch Solution

Google Gemini (gemini-2.5-flash) • CVE: CVE-2026-30240

Unknown
N/A
⚠️ Vulnerability Description:

1. IMMEDIATE ACTIONS

Upon notification or suspicion of compromise related to CVE-2026-30240, immediate actions are critical to contain potential damage.

a. Emergency Network Segmentation: Immediately isolate any GlobalNet Devices NetworkOS appliances running affected versions (1.0 through 1.5) from public internet access. If possible, place management interfaces on a dedicated, isolated management network VLAN with no routing to untrusted segments.
b. Restrict Management Access: Implement emergency firewall rules (ACLs) on upstream network devices to strictly limit inbound access to the GlobalNet NetworkOS management interface ports (typically TCP/443 or TCP/8443) to only trusted administrative IP addresses or subnets. Block all other ingress traffic to these ports.
c. Review Logs for Indicators of Compromise (IOCs): Scrutinize device logs (system logs, web server access logs, authentication logs) on affected GlobalNet devices and surrounding network infrastructure (firewalls, IDS/IPS) for any suspicious activity dating back several weeks. Look for unusual process executions, unexplained reboots, unexpected configuration changes, unauthorized access attempts, or outbound connections from the device to unknown external hosts.
d. Prepare for Patching: Identify all GlobalNet NetworkOS devices in your environment that are running vulnerable versions. Prepare a change management plan for applying the forthcoming security patch, including identifying maintenance windows and rollback procedures.
e. Incident Response Team Activation: Engage your internal or external incident response team to assess the scope of potential compromise and guide further actions.

2. PATCH AND UPDATE INFORMATION

GlobalNet Devices is expected to release security patches to address CVE-2026-30240. It is imperative to apply these updates as soon as they become available and are validated in your environment.

a. Vendor Advisory Monitoring: Continuously monitor GlobalNet Devices' official security advisories, support portals, and mailing lists for the release of the official security patch for NetworkOS versions 1.0 through 1.5.
b. Patch Availability: The vendor is anticipated to release NetworkOS version 1.5.1 (or similar) as the remediation for this vulnerability. Ensure you download patches only from official GlobalNet Devices sources.
c. Patch Application Procedure: Follow GlobalNet Devices' specific instructions for applying the patch. This typically involves downloading the firmware image, verifying its integrity (e.g., via checksums or digital signatures), and applying it through the device's management interface or command-line interface. Ensure proper backup of device configurations is performed prior to updating.
d. Test in Staging Environment: If feasible, test the patch in a non-production or staging environment to confirm stability and functionality before widespread deployment.
e. Verify Patch Installation: After applying the patch, verify that the

💡 AI-generated — review with a security professional before acting.View on NVD →
Post Views: 5

Site map

  • About Us
  • Privacy Policy
  • Terms & Conditions of Use
©2026 | Design: Newspaperly WordPress Theme