gitsafehub
github.com/gioboa/angular-ssr-vercel ↗

gioboa/angular-ssr-vercel

scanned 2026-08-11 · git 4bf9c31
2 of 6 checks flagged a security issue
🔴 Needs attention
Only 4 of 6 checks finished — treat this as provisional. Re-check ↻

Informational scan, not a security audit. How this is computed.

Leaked secrets✓Vulnerable dependencies36Known OSS vulnerabilities120Risky code patterns✓Malicious dependencies—Project health—

Security checks

Leaked secrets — Gitleaksⓘ none found ✓

API keys, passwords or tokens committed into the repo.

Nothing found by this check. ✓

via Gitleaks v8.21.2 · MIT

Vulnerable dependencies — Trivyⓘ 36 found · 1 serious

Packages you depend on that have known security holes (CVEs).

  • Serious CVE-2026-27739 Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-27739). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-66035 angular: Angular HTTP Client Has XSRF Token Leakage via Protocol-Relative URLs
    package-lock.json
    A package you depend on has a known security hole (CVE-2025-66035). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50170 @angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-50170). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50171 @angular/common: Angular @angular/common: Denial of Service via malformed digitsInfo parameter
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-50171). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54266 @angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-54266). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54268 @angular/common: Angular @angular/common: Denial of Service via crafted date format string
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-54268). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-68945 @angular/common: Angular: Cross-Request Response Reuse and State Poisoning in HttpTransferCache
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-68945). Fix: Update that package to its patched version.
  • Worth fixing CVE-2025-66412 angular: Angular Stored XSS Vulnerability via SVG Animation, SVG URL and MathML Attributes
    package-lock.json
    A package you depend on has a known security hole (CVE-2025-66412). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-22610 angular: Angular: Cross-site scripting vulnerability in Template Compiler
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-22610). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-32635 @angular/core: @angular/compiler: Angular has XSS in i18n attribute bindings
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-32635). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69151 @angular/compiler: @angular/core: Angular: Cross-Site Scripting via internationalization event handlers
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-69151). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50557 @angular/compiler: @angular/core: Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-50557). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54265 @angular/compiler: Angular: Two-Way Property Binding Sanitization Bypass (XSS)
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-54265). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-22610 angular: Angular: Cross-site scripting vulnerability in Template Compiler
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-22610). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-27970 @angular/core: Angular: Cross-site scripting via compromised translation files
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-27970). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-32635 @angular/core: @angular/compiler: Angular has XSS in i18n attribute bindings
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-32635). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-54267 @angular/core: Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-54267). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-69151 @angular/compiler: @angular/core: Angular: Cross-Site Scripting via internationalization event handlers
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-69151). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50557 @angular/compiler: @angular/core: Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-50557). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-52725 @angular/core: @angular/core: Cross-Site Scripting (XSS) via dynamic component creation bypass
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-52725). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-41423 Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-41423). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-46417 @angular/platform-server: Angular: SSRF via Hostname Hijacking in @angular/platform-server
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-46417). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50168 @angular/platform-server: Angular @angular/platform-server: Server-Side Request Forgery (SSRF) via malformed URL parsing
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-50168). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50555 @angular/platform-server: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-50555). Fix: Update that package to its patched version.
  • Worth fixing CVE-2026-50556 @angular/platform-server: domino: Angular Platform Server: Cross-Site Scripting via unescaped `</noscript>` tags in dynamic content
    package-lock.json
    A package you depend on has a known security hole (CVE-2026-50556). Fix: Update that package to its patched version.
… 11 more not shown

via Trivy v0.70.0 · Apache-2.0

Known OSS vulnerabilities — OSV-Scannerⓘ 120 found · 5 serious

Your dependencies cross-checked against the OSV vulnerability database.

  • Serious GHSA-g93w-mfhg-p222 Angular vulnerable to XSS in i18n attribute bindings
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-32635). Fix: Update that package to its patched version.
  • Serious GHSA-g93w-mfhg-p222 Angular vulnerable to XSS in i18n attribute bindings
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-32635). Fix: Update that package to its patched version.
  • Serious GHSA-x288-3778-4hhx Angular SSR is vulnerable to SSRF and Header Injection via request handling pipeline
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-27739). Fix: Update that package to its patched version.
  • Serious GHSA-wf6x-7x77-mvgw Immutable is vulnerable to Prototype Pollution
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-29063). Fix: Update that package to its patched version.
  • Serious GHSA-23hp-3jrh-7fpw node-tar: Decompression/parse DoS via unlimited input
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-59873). Fix: Update that package to its patched version.
  • Worth fixing GHSA-39pv-4j6c-2g6v @angular/common: Weak 32-Bit Cache Key Hashing in `HttpTransferCache` Leading to Cross-Request Data Leakage and State Poisoning
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54266). Fix: Update that package to its patched version.
  • Worth fixing GHSA-48r7-hpm6-gfxm @angular/common: Denial of Service (DoS) via OOM in Date Formatting (formatDate)
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54268). Fix: Update that package to its patched version.
  • Worth fixing GHSA-58c5-g7wp-6w37 Angular is Vulnerable to XSRF Token Leakage via Protocol-Relative URLs in Angular HTTP Client
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2025-66035). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jhpw-976m-542j Angular: Cache-Key Ambiguity in HttpTransferCache Leading to Cross-Request Response Reuse and State Poisoning
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-68945). Fix: Update that package to its patched version.
  • Worth fixing GHSA-p3vc-36g9-x9gr @angular/common: Denial of Service (DoS) via OOM in Number Formatting (digitsInfo)
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-50171). Fix: Update that package to its patched version.
  • Worth fixing GHSA-q6f4-qqrg-jv6x @angular/common: Information Leak via Default Caching of Credentialed Requests in HttpTransferCache
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-50170). Fix: Update that package to its patched version.
  • Worth fixing GHSA-58w9-8g37-x9v5 @angular/compiler: Two-Way Property Binding Sanitization Bypass (XSS)
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54265). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f3m7-gqxr-g87x Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-50557). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jj27-h5hq-8x99 Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-69151). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jrmj-c5cx-3cw6 Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-22610). Fix: Update that package to its patched version.
  • Worth fixing GHSA-v4hv-rgfq-gp49 Angular Stored XSS Vulnerability via SVG Animation, SVG URL and MathML Attributes
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2025-66412). Fix: Update that package to its patched version.
  • Worth fixing GHSA-692r-grfm-v8x7 @angular/core: Angular Template and Dynamic Component Namespace Bypass leading to Cross-Site Scripting (XSS)
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-52725). Fix: Update that package to its patched version.
  • Worth fixing GHSA-f3m7-gqxr-g87x Angular: Template and Attribute Namespace Sanitization Bypass (XSS)
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-50557). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jj27-h5hq-8x99 Angular i18n: Cross-Site Scripting (XSS) via event-handler attributes
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-69151). Fix: Update that package to its patched version.
  • Worth fixing GHSA-jrmj-c5cx-3cw6 Angular has XSS Vulnerability via Unsanitized SVG Script Attributes
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-22610). Fix: Update that package to its patched version.
  • Worth fixing GHSA-prjf-86w9-mfqv Angular i18n vulnerable to Cross-Site Scripting
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-27970). Fix: Update that package to its patched version.
  • Worth fixing GHSA-rgjc-h3x7-9mwg Angular Client Hydration DOM Clobbering & Response-Cache Poisoning
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-54267). Fix: Update that package to its patched version.
  • Worth fixing GHSA-45q2-gjvg-7973 Angular: SSRF via protocol-relative and backslash URLs in Angular Platform-Server
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-41423). Fix: Update that package to its patched version.
  • Worth fixing GHSA-gxx4-3xcv-f8qx @angular/platform-server: Missing `<noscript>` Raw-Text Serialization Escaping leads to Cross-Site Scripting (XSS) in Angular SSR
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-50556). Fix: Update that package to its patched version.
  • Worth fixing GHSA-hqr9-c56f-3x7f @angular/platform-server: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
    /workdirs/scan-bfbacf79-a6fa-4b69-af6c-449c5bbff3b9/package-lock.json
    A package you depend on has a known security hole (CVE-2026-50555). Fix: Update that package to its patched version.
… 95 more not shown

via OSV-Scanner v1.9.2 · Apache-2.0

Risky code patterns — Semgrepⓘ none found ✓

Code that can be exploited: injection, hardcoded credentials and similar.

Nothing found by this check. ✓

via Semgrep v1.147.0 · LGPL-2.1

Malicious dependencies — Guarddogⓘ timed out

Packages that look intentionally malicious: typosquats, sneaky install scripts.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via Guarddog v2.10.0 · Apache-2.0

error: npm:timeout

Project health

A signal about how the project is maintained — not a vulnerability in your code. It doesn’t affect the verdict above.

Project health — OpenSSF Scorecardⓘ didn’t run

Maintenance & supply-chain hygiene. A signal about the project, not a vulnerability in your code.

This check didn’t finish — that’s not the same as “clean.” Try Check again above.

via OpenSSF Scorecard · Apache-2.0

About these results. Six open-source checks ran in parallel; every finding is tagged with the tool that produced it. The verdict follows a published rule. False positives and false negatives are normal — a clean scan does not mean the code is secure, and a red verdict does not mean the project is compromised.