SYSTEM code execution via writable server directory
Published Apr 3, 2026 · Updated Apr 3, 2026
Incorrect default permissions in Airbus TETRA Connectivity Server 7.0 allow local users to execute code as SYSTEM via a crafted file. A vulnerable directory permits placement of a crafted file that the installed server later executes with SYSTEM privileges. The attack requires low-privileged local access and active user interaction; Airbus has not disclosed the directory name or triggering service action.
Summary
What happened
Incorrect default permissions in Airbus TETRA Connectivity Server 7.0 allow local users to execute code as SYSTEM via a crafted file. A vulnerable directory permits placement of a crafted file that the installed server later executes with SYSTEM privileges. The attack requires low-privileged local access and active user interaction; Airbus has not disclosed the directory name or triggering service action.
The record
- CVE
- CVE-2025-7024
- Published
- Apr 3, 2026
- Updated
- Apr 3, 2026
- Vendor
- Airbus
- Product
- TETRA Connectivity Server
- Classifications
- CWE-276, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 3, 2026CVE publishedPublication date reported by the CVE source.
- Apr 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=7.0
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo