Skip to main content
CVE-2025-57802VulnerabilityPublished

CVE-2025-57802: airlinklabs daemon · UNIX Symbolic Link (Symlink) Following

Affects airlinklabs daemonSource CVE Database V5

0

Not known to be exploited · CVSS 8.7 High · fixed in 1.0.1 : patch airlinklabs daemon soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 33% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.1
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
airlinklabs daemonAffected
  • =1.0.0
Fixed in–

AI-suggested

1. Immediate upgrade to Airlinklabs daemon version 1.0.1 or later, which contains the patch that properly restricts symlink following and prevents unauthorized host file access. 2. Implement strict access controls and monitoring on container environments to limit who can access and modify container filesystems, especially mounted volumes. 3. Avoid bind-mounting arbitrary or sensitive host paths into containers unless absolutely necessary, and if required, restrict mount points to non-sensitive directories with minimal permissions. 4. Employ container security tools that detect and alert on suspicious symlink creation or unusual file access patterns within containers. 5. Use container runtime security policies (e.g., seccomp, AppArmor, SELinux) to restrict daemon and container process capabilities related to filesystem access. 6. Conduct regular audits of container configurations and mounted volumes to ensure no unauthorized symlinks or mounts exist. 7. Educate DevOps and security teams about the risks of symlink attacks and the importance of secure container volume management. 8. Consider network segmentation and zero-trust principles to limit the impact if a container is compromised.

Description

Airlink's Daemon interfaces with Docker and the Panel to provide secure access for controlling instances via the Panel. In version 1.0.0, an attacker with access to the affected container can create symbolic links inside the mounted directory (/app/data). Because the container bind-mounts an arbitrary host path, these symlinks can point to sensitive locations on the host filesystem. When the application or other processes follow these symlinks, the attacker can gain unauthorized read access to host files outside the container. This issue has been patched in version 1.0.1.

References

Community reviews

Loading reviews…