Security readout for executives and security teams
Plain-English summary
An unauthenticated attacker can make a vulnerable QD server contact internal systems or cloud metadata services. This could expose sensitive information or let the attacker interact with services normally unreachable from the internet. Disabled TLS certificate verification further weakens request safety.
Executive priority
Prioritize immediate exposure assessment and containment for internet-facing QD systems. The vulnerability can cross network trust boundaries without credentials and may expose high-value internal data. Escalate remediation where QD has broad internal or cloud access.
Technical view
QD releases 20220208 through 20250803 contain SSRF in /har/test. Fetcher.build_request() creates requests from user-controlled JSON without restricting schemes, hosts, or IP ranges. The endpoint requires no authentication, and validate_cert is false. The supplied CVSS 3.1 score is 9.1.
Likely exposure
Exposure is likely where an affected QD deployment makes /har/test remotely reachable. Risk increases when the server can access private network services, cloud metadata endpoints, or privileged management interfaces. The bundle’s structured product metadata is incomplete, so confirm deployed software and versions directly.
Exploitation context
The issue is remotely reachable, unauthenticated, and low complexity according to the supplied CVSS vector. However, it is not listed as KEV, and the provided sources do not establish active exploitation. Treat practical exploitability as high without claiming observed attacks.
Researcher notes
The core weakness is missing outbound-request destination validation in libs/fetcher.py, compounded by unauthenticated handler access and disabled certificate validation. The bundle names affected releases but supplies no official patch version. Avoid inferring a fixed release; verify project guidance and test controls safely.
Mitigation direction
- Check current QD vendor or project guidance for a corrected release or supported mitigation.
- Restrict or disable external access to /har/test until remediation is confirmed.
- Limit QD server egress to approved destinations and block private, loopback, link-local, and metadata ranges.
- Require authentication and authorization before permitting request-testing functionality.
- Restore TLS certificate validation for outbound HTTPS requests where supported.
Validation and detection
- Inventory QD deployments and compare installed versions with 20220208 through 20250803.
- Confirm whether /har/test is reachable without authentication from untrusted networks.
- Review outbound firewall policy for access to internal services and cloud metadata addresses.
- Inspect application and proxy logs for unusual /har/test requests or unexpected outbound destinations.
- Verify remediation rejects disallowed schemes, private addresses, redirects, and invalid TLS certificates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-918: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCloud metadata behavior lookup
The CVE wording references SSRF or metadata access, so cloud discovery and credential material review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-51152 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://qd-today.github.io/qd/CVE reference, mitre
- https://gist.github.com/kurokoleung/98e950e3e05205fc57d2029ad68a702eCVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Server-Side Request Forgery (SSRF)
Server-Side Request Forgery (SSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.