CVE-2026-7065: BidingCC BuildingAI SSRF Vulnerability

CVE-2026-7065 Overview

A Server-Side Request Forgery (SSRF) vulnerability has been identified in BidingCC BuildingAI versions up to 26.0.1. The vulnerability exists in the uploadRemoteFile function within the file packages/core/src/modules/upload/services/file-storage.service.ts of the Remote Upload API component. An attacker can manipulate the url argument to perform unauthorized server-side requests, potentially accessing internal resources or services that should not be publicly accessible.

Critical Impact
This SSRF vulnerability allows unauthenticated remote attackers to make arbitrary HTTP requests from the server, potentially leading to unauthorized access to internal services, cloud metadata endpoints, or sensitive internal network resources.

Affected Products

BidingCC BuildingAI versions up to and including 26.0.1
Remote Upload API component
File storage service module (file-storage.service.ts)

Discovery Timeline

2026-04-27 - CVE-2026-7065 published to NVD
2026-04-29 - Last updated in NVD database

Technical Details for CVE-2026-7065

Vulnerability Analysis

This vulnerability is classified as CWE-918: Server-Side Request Forgery (SSRF). The affected function uploadRemoteFile in the file storage service accepts a user-controlled URL parameter without proper validation or sanitization. When processing remote file uploads, the application makes server-side HTTP requests to fetch content from the provided URL, trusting the input without verifying whether the target destination is safe or authorized.

The network-accessible nature of this vulnerability means attackers can exploit it remotely without requiring any authentication or user interaction. The exploit has been publicly disclosed and may already be in use, increasing the urgency for remediation.

Root Cause

The root cause of this vulnerability lies in insufficient input validation of the url parameter in the uploadRemoteFile function. The application fails to implement proper URL validation, allowlisting, or blocklisting mechanisms that would prevent requests to internal or sensitive endpoints. Without these controls, an attacker can craft malicious URLs pointing to internal services, localhost addresses, or cloud metadata endpoints (such as 169.254.169.254 for AWS/Azure/GCP metadata services).

Attack Vector

The attack can be initiated remotely over the network. An attacker can send a crafted request to the Remote Upload API endpoint, providing a malicious URL as the url parameter. The server will then make an HTTP request to this attacker-controlled destination. Common exploitation scenarios include:

Internal Service Enumeration: Scanning internal network services by observing response differences
Cloud Metadata Access: Retrieving sensitive cloud credentials from metadata endpoints
Bypassing Network Restrictions: Accessing services that are only available from the internal network
Data Exfiltration: Reading sensitive files or data from internal systems

The vulnerability has been documented in the GitHub Issue Discussion where technical details of the exploitation method are available.

Detection Methods for CVE-2026-7065

Indicators of Compromise

Unusual outbound HTTP requests from the application server to internal IP ranges (10.x.x.x, 172.16.x.x, 192.168.x.x)
Requests to cloud metadata endpoints (169.254.169.254) originating from the BuildingAI application
High volume of requests to the Remote Upload API endpoint with varying URL parameters
Error logs indicating failed connections to internal services or localhost

Detection Strategies

Monitor application logs for requests to the uploadRemoteFile endpoint with suspicious URL patterns
Implement network-level monitoring to detect outbound requests from the application server to internal IP ranges or metadata services
Deploy Web Application Firewall (WAF) rules to detect and block SSRF attack patterns in URL parameters
Use intrusion detection systems to alert on anomalous outbound traffic patterns from the affected service

Monitoring Recommendations

Enable detailed logging for the Remote Upload API component to capture all URL parameters
Set up alerts for requests containing localhost, internal IP addresses, or cloud metadata endpoints in URL parameters
Monitor for data exfiltration patterns following successful SSRF exploitation attempts
Review access logs regularly for patterns indicating systematic internal network scanning

How to Mitigate CVE-2026-7065

Immediate Actions Required

Disable or restrict access to the Remote Upload API functionality until a patch is available
Implement network-level controls to prevent the application server from making requests to internal IP ranges
Deploy WAF rules to block SSRF attack patterns targeting the uploadRemoteFile endpoint
Contact BidingCC regarding the security issue, as the vendor has not yet responded to the initial disclosure

Patch Information

As of the last update on 2026-04-29, no official patch has been released by BidingCC. The project maintainers were notified early through an issue report but have not responded. Organizations should monitor the GitHub Project Repository for updates and consider implementing the workarounds below until an official fix is available.

Additional technical details are available at the VulDB Vulnerability Entry.

Workarounds

Implement URL validation to restrict allowed schemes to http and https only
Create an allowlist of trusted domains that the Remote Upload API can access
Block requests to private IP ranges (RFC 1918), localhost, and cloud metadata IP addresses at the application level
Consider using a network proxy that enforces URL restrictions for all outbound requests from the application

bash

# Example: Firewall rules to block internal requests from the application server
# Block requests to private IP ranges
iptables -A OUTPUT -m owner --uid-owner buildingai-user -d 10.0.0.0/8 -j DROP
iptables -A OUTPUT -m owner --uid-owner buildingai-user -d 172.16.0.0/12 -j DROP
iptables -A OUTPUT -m owner --uid-owner buildingai-user -d 192.168.0.0/16 -j DROP
iptables -A OUTPUT -m owner --uid-owner buildingai-user -d 127.0.0.0/8 -j DROP
# Block cloud metadata endpoint
iptables -A OUTPUT -m owner --uid-owner buildingai-user -d 169.254.169.254 -j DROP