Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach AA Server over network
-
ExploitAbuse allowed unauthenticated endpoint creation
-
ExecutionRepeatedly recreate endpoints
-
ImpactTrigger excessive resource allocation and low-impact exposure
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V13 - Configuration Secure default settings
|
| Exploitation Conditions | Exploitable only when the server is configured to allow creation/recreation of Unauthenticated Endpoints with an empty whitelist, which the vendor states permits all networks to create/recreate endpoints. This is the AT:P attack requirement in the CVSS 4.0 vector. Exploitation is eliminated by the documented secure configuration: disallow Unauthenticated Endpoint creation entirely, or, if required, specify trusted networks via a non-empty whitelist. Limiting factors: the insecure state is a configuration choice rather than the shipped behavior the vendor now recommends, the recorded impact is only low confidentiality (no integrity or availability), and upgrading to 6.6.2.0 surfaces a best-practice warning when the configuration is unsecure. |
| Impact | This is a low-priority issue, and the available signals are consistent on that. The vendor-supplied CVSS 4.0 base score is 2.9 (Low), the vuln.today Decision label is 'monitor', and there is no CISA KEV listing, so there is no evidence of active exploitation. The impact is narrow: the 4.0 vector sets VC:L and VI:N/VA:N, meaning only low confidentiality impact and no integrity or availability impact recorded, despite the CWE being Excessive Allocation (CWE-1188, insecure default). The vector also carries AT:P (an attack requirement must be met) and the mitigation text confirms the flaw only manifests under a specific insecure configuration (unauthenticated endpoint creation allowed with an empty whitelist), so this is not a default-config, no-conditions remote bug. One conflicting signal to flag explicitly: the CVSS 4.0 vector contains E:P (proof-of-concept exploit maturity), yet no PoC or exploit reference appears anywhere in the provided sources - the four references are all vendor documentation pages. EPSS is not provided, so widespread-exploitation probability cannot be assessed. Net: a genuine but low-severity, configuration-dependent misconfiguration risk, not an urgent patch item. |
| Exploit ScenarioDerived | An OpenText Advanced Authentication Server is deployed with the insecure configuration that permits creation/recreation of Unauthenticated Endpoints from any network (an empty whitelist allows all networks). A remote attacker who can reach the server abuses this to create or recreate endpoints, causing excessive resource allocation and a limited information exposure. No PoC or exploit reference is included in the supplied sources, though the vendor CVSS 4.0 vector asserts E:P (proof-of-concept maturity). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
An insecure default in OpenText Advanced Authentication Server lets a deployment run with an empty trusted-network whitelist for Unauthenticated Endpoints, so any network can create or recreate those endpoints, causing excessive resource allocation and limited information exposure. Affected branches are 6.4.0.0 through 6.4.3.x, 6.5.0.0 through 6.5.0.x, and 6.6.0.0 through 6.6.1.0, and the weakness only materialises when administrators have left that configuration in its permissive state (the AT:P attack requirement in the CVSS 4.0 vector). Recorded impact is low confidentiality only, with no integrity or availability effect, and the assigned CVSS 4.0 base score of 2.9 with an E:P exploit-maturity rating means a public proof-of-concept reference is recorded but is not verified as working exploit code; there is no KEV entry, and the vendor-reported issue carries a monitor priority. The vendor's own remediation framing confirms the fix is a secure configuration plus the 6.6.2.0 release that flags unsecure settings.
RemediationAI
The vendor's stated fix is a secure configuration rather than code alone: change the server configuration so creation and recreation of Unauthenticated Endpoints is not allowed at all, and if those endpoints are genuinely required, set a non-empty whitelist naming only trusted networks - an empty whitelist permits all networks to create or recreate endpoints. Upgrade to 6.6.2.0 (vendor-released patch; security-improvements-662), or to the branch releases 6.4.3.9 and 6.5.0.11 documented in the security-improvements-6439 and security-improvements-65011 advisories, since 6.6.2.0 adds a best-practice entry that surfaces a warning when the configuration is unsecure. Note the trade-off: applying the 6.6.2.0 best-practice check without changing the whitelist only raises a warning and leaves the permissive state in place, and disabling unauthenticated endpoint creation/recreation entirely will break workflows that depend on it, which is why the non-empty whitelist option exists. No vendor-side workaround beyond configuration is described in the available references.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-1188 (Initialization of a Resource with an Insecure Default) applies to the endpoint-provisioning feature of the Advanced Authentication Server: the service supports creation and recreation of Unauthenticated Endpoints, gated by a whitelist of trusted networks, and that whitelist initialises empty. Per the vendor, an empty whitelist does not mean "deny all" - it means every network is permitted to create or recreate endpoints, which is the insecure default and the root cause of the reported excessive allocation. The CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/R:A/V:D/RE:L/U:Amber) marks the flaw as network reachable and automatable but dependent on a specific attack requirement - the permissive whitelist state - while recording only low confidentiality impact and no integrity or availability loss. The independent assessment restates this more conservatively as CVSS 3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N, where the high attack complexity captures the configuration prerequisite rather than any algorithmic or timing condition; the trigger beyond the whitelist precondition is not described in the available sources. Because the vulnerable state is a deployment choice rather than unavoidable shipped behaviour, exposure is confined to installations that both enable unauthenticated endpoint creation/recreation and leave the whitelist empty.
Know when Advanced Authentication Server gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/AU:Y/R:A/V:D/RE:L/U:Amber
Network-reachable and unauthenticated (AV:N/PR:N), but requires the insecure empty-whitelist configuration (AC:H); only low confidentiality impact, no integrity or availability impact.
Primary rating from Vendor (OpenText).
CVSS VectorVendor: OpenText
DescriptionCVE.org
Initialization of a resource with an insecure default vulnerability in OpenText Advanced Authentication Server allows Excessive Allocation.
This issue affects Advanced Authentication Server: from 6.4.0.0 through 6.4.3.x, from 6.5.0.0 through 6.5.0.x, and from 6.6.0.0 through 6.6.1.0.
The fix for this is issue is to create a secure configuration. The 6.6.2.0 release has a best practice entry if the configuration is unsecure.
A secure configuration is to NOT allow creation/recreation of Unauthenticated Endpoints. If creation/recreation of Unauthenticated Endpoints is required, you should only allow it from trusted networks.
To remedy this issue, change your configuration to NOT allow creation/recreation of Unauthenticated Endpoints. If you require Unauthenticated Endpoints, you MUST change your configuration to use a non-empty whitelist to specify the trusted networks. An empty whitelist will allow all networks to create/recreate endpoints.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-113002
GHSA-m3px-g696-rxgm
NVD
CVE.org
EPSS
Exploit-DB