Skip to main content

AiraHub2 EUVD-2026-25657

| CVE-2026-6981 LOW
Server-Side Request Forgery (SSRF) (CWE-918)
2026-04-25 VulDB
2.1
CVSS 4.0 · NVD

Severity by source

NVD PRIMARY
2.1 LOW
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
X

Lifecycle Timeline

8
Severity Changed
Apr 29, 2026 - 01:12 NVD
MEDIUM LOW
CVSS changed
Apr 29, 2026 - 01:12 NVD
5.3 (MEDIUM) 2.1 (LOW)
PoC Detected
Apr 29, 2026 - 01:00 vuln.today
Public exploit code
CVSS changed
Apr 25, 2026 - 15:22 NVD
6.3 (MEDIUM) 5.3 (MEDIUM)
Analysis Generated
Apr 25, 2026 - 15:00 vuln.today
EUVD ID Assigned
Apr 25, 2026 - 14:30 euvd
EUVD-2026-25657
Analysis Generated
Apr 25, 2026 - 14:30 vuln.today
CVE Published
Apr 25, 2026 - 14:15 nvd
LOW 2.1

DescriptionCVE.org

A vulnerability was found in IhateCreatingUserNames2 AiraHub2 up to 3e4b77fd7d48ed811ffe5b8d222068c17c76495e. Affected is the function connect_stream_endpoint/sync_agents of the file AiraHub.py of the component Endpoint. Performing a manipulation results in server-side request forgery. The attack may be initiated remotely. The exploit has been made public and could be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. Multiple endpoints are affected. The vendor was contacted early about this disclosure but did not respond in any way.

AnalysisAI

Server-side request forgery (SSRF) in AiraHub2 allows authenticated remote attackers to manipulate the connect_stream_endpoint and sync_agents functions in AiraHub.py, enabling arbitrary HTTP requests to internal or external systems. The vulnerability affects multiple endpoints and has publicly available exploit code; however, the vendor has not responded to disclosure attempts and uses a rolling release model, making patch status unclear.

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Authenticate to AiraHub2
Delivery
Access connect_stream_endpoint or sync_agents function
Exploit
Provide malicious URL parameter
Execution
Server makes request to attacker-specified endpoint
Impact
Attacker exfiltrates internal data or modifies backend state

Vulnerability AssessmentAI

Exploitation Authentication is required: the CVSS PR:L vector confirms that exploitation requires login credentials or an authenticated session on AiraHub2. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment CVSS 6.3 (Medium) reflects network-accessible exploitation (AV:N) with low complexity (AC:L) but requiring authenticated access (PR:L), limited scope (SU), and low confidentiality/integrity/availability impact. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An authenticated user with access to AiraHub2 (e.g., a low-privileged operator or compromised credential) calls the connect_stream_endpoint or sync_agents function with a crafted parameter that specifies an arbitrary URL pointing to an internal service (e.g., http://192.168.1.100:8080/admin or http://localhost:6379). The AiraHub2 server, trusting the endpoint parameter, makes an HTTP request to that internal address on behalf of the attacker. …
Remediation Because the vendor has not provided a patched release and AiraHub2 uses a rolling commit-based release model rather than semantic versioning, patching requires pulling from the source repository (likely GitHub) and verifying that the deployed commit is newer than the vulnerable 3e4b77fd7d48ed811ffe5b8d222068c17c76495e. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

EUVD-2026-25657 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy