{
  "@id": "urn:uuid:db1b9ef1-8aef-4337-9d49-7a69ee960060",
  "role": "Document Creator",
  "author": "https://tuxcare.com",
  "version": 1,
  "@context": "https://openvex.dev/ns/v0.2.0",
  "timestamp": "2026-09-30T13:29:39.589848+00:00",
  "statements": [
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40angular/create@19.2.27-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40angular/create@19.2.27-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-30T13:29:39.589848+00:00",
      "status_notes": "Vulnerability CVE-2026-27738 does not affect version 19.2.27-tuxcare.1 of @angular/create. not_affected \u2014 The target Angular CLI/DevKit version 19.2.27 is not affected by CVE-2026-27738 (Open Redirect via X-Forwarded-Prefix). The upstream vendor fix is already present in the shipped code. Both security defenses are in place: (1) joinUrlParts function strips ALL leading/trailing slashes via while loops (lines 110-116 in url.ts), preventing protocol-relative URL formation like //evil.com, and (2) VAL...",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-27738"
      },
      "impact_statement": "not_affected \u2014 The target Angular CLI/DevKit version 19.2.27 is not affected by CVE-2026-27738 (Open Redirect via X-Forwarded-Prefix). The upstream vendor fix is already present in the shipped code. Both security defenses are in place: (1) joinUrlParts function strips ALL leading/trailing slashes via while loops (lines 110-116 in url.ts), preventing protocol-relative URL formation like //evil.com, and (2) VAL..."
    },
    {
      "status": "not_affected",
      "products": [
        {
          "@id": "pkg:npm/%40angular/create@19.2.27-tuxcare.1",
          "identifiers": {
            "purl": "pkg:npm/%40angular/create@19.2.27-tuxcare.1"
          }
        }
      ],
      "timestamp": "2026-09-30T13:29:39.589848+00:00",
      "status_notes": "Vulnerability CVE-2026-27739 does not affect version 19.2.27-tuxcare.1 of @angular/create. The target repository (angular-cli v19.2.27) is not affected by CVE-2026-27739 (SSRF via unvalidated HTTP headers in Angular SSR). The vulnerability was fixed by the upstream vendor (Google/Angular team) in commit 2a72d7483d87ccdcfa0c5148f34a4c6ebb6c6cf9, authored by alanagius@google.com, which was included in upstream release v19.2.21. The current target version v19.2.27 includes this fix through normal upstream progression (not through a TuxCare backport). The fix introduces comprehensive validation of Host, X-Forwarded-Host, X-Forwarded-Port, and X-Forwarded-Proto headers, blocking malicious header values before they can be used to construct URLs for server-side HTTP requests.",
      "justification": "vulnerable_code_not_present",
      "vulnerability": {
        "name": "CVE-2026-27739"
      },
      "impact_statement": "The target repository (angular-cli v19.2.27) is not affected by CVE-2026-27739 (SSRF via unvalidated HTTP headers in Angular SSR). The vulnerability was fixed by the upstream vendor (Google/Angular team) in commit 2a72d7483d87ccdcfa0c5148f34a4c6ebb6c6cf9, authored by alanagius@google.com, which was included in upstream release v19.2.21. The current target version v19.2.27 includes this fix through normal upstream progression (not through a TuxCare backport). The fix introduces comprehensive validation of Host, X-Forwarded-Host, X-Forwarded-Port, and X-Forwarded-Proto headers, blocking malicious header values before they can be used to construct URLs for server-side HTTP requests."
    }
  ]
}