{
  "asset": {
    "id": "6acf1dd1f2bbb17afa14ee19",
    "name": "adieuu",
    "version": "0.4.41",
    "type": "asset",
    "vulnerabilities": [
      {
        "cveId": "CVE-2026-112949",
        "onCISAKev": false,
        "triageStatus": "Not Triaged",
        "description": "Vitest is a Vite-native testing framework for JavaScript and TypeScript projects. From 2.1.0-beta.7 until 4.1.12 and 5.0.3, an unauthenticated non-browser WebSocket client that can reach a development server using interceptorPlugin can register a manual mock whose attacker-controlled url createManualModuleSource inserts unescaped into generated module source. When the developer browser loads the affected module, attacker-controlled JavaScript executes on the development-server origin. This issue is fixed in versions 4.1.12 and 5.0.3.",
        "publishedDate": "2026-10-20T16:17:05.660Z",
        "cvssScore": 4.7,
        "cvssSeverity": "MEDIUM",
        "epssPercentile": 0.14472,
        "affectedComponents": [
          "pkg:npm/%40vitest/mocker@5.0.1"
        ],
        "source": "OSV"
      },
      {
        "cveId": "CVE-2026-112950",
        "onCISAKev": false,
        "triageStatus": "Not Triaged",
        "description": "Vitest is a Vite-native testing framework for JavaScript and TypeScript projects. From 4.1.11 until 4.1.12 and 5.0.3, isFileLoadingAllowed and the filesystem read interpret backslashes differently on Windows in packages/mocker/src/node/interceptorPlugin.ts. When a client can reach the Vite dev server on Windows and register a redirect mock containing backslash traversal, POSIX joining preserves a Windows backslash traversal that the later filesystem read interprets as a path separator, so the client can read a file outside server.fs.allow that the Vitest process can access. This issue is fixed in versions 4.1.12 and 5.0.3.",
        "publishedDate": "2026-10-20T16:17:05.807Z",
        "cvssScore": 5.9,
        "cvssSeverity": "MEDIUM",
        "epssPercentile": 0.31093,
        "affectedComponents": [
          "pkg:npm/%40vitest/mocker@5.0.1"
        ],
        "source": "OSV"
      },
      {
        "cveId": "CVE-2023-29827",
        "onCISAKev": false,
        "triageStatus": "NotAffected",
        "description": "ejs v3.1.9 is vulnerable to server-side template injection. If the ejs file is controllable, template injection can be implemented through the configuration settings of the closeDelimiter parameter. NOTE: this is disputed by the vendor because the render function is not intended to be used with untrusted input.",
        "publishedDate": "2023-05-04T14:15:11.363Z",
        "cvssScore": 9.8,
        "cvssSeverity": "CRITICAL",
        "epssPercentile": 0.92824,
        "affectedComponents": [
          "pkg:npm/ejs@6.0.1"
        ],
        "justification": "vulnerableCodeIsNotInExecutePath",
        "scope": "allVersionsOfThisAssetForever",
        "statusNotes": "No fix needed. No ejs version resolves this finding, and upgrading (latest is 7.0.2) wouldn't clear it. The ejs: \"6.0.1\" override in pnpm-workspace.yaml stays. Re-check if ejs ever ships in a runtime package, if templates ever come from outside the repo, or if the advisory gets a real affected range.",
        "source": "NVD"
      },
      {
        "cveId": "CVE-2026-110725",
        "onCISAKev": false,
        "triageStatus": "Not Triaged",
        "description": "fast-uri is a dependency-free RFC 3986 URI parser and serializer for Node.js. In versions before 2.4.8, from 3.0.0 through 3.1.8, and from 4.0.0 through 4.2.2, when serialize(), normalize(), or resolve() are called with the non-default option reference set to suffix on a reference that has no authority, the emitted relative reference can contain a bare colon in its first path segment without escaping it, even though RFC 3986 forbids that because it makes the string reparse as an absolute URI with a scheme. An application that serializes or normalizes a relative reference with the suffix option and then treats the result as a URI can turn inert input into a live javascript, data, or vbscript URL, a cross-site scripting vector, and the equal() comparison can conflate a scheme-bearing reference with a relative one. Exposure is limited to applications using the non-default suffix reference option. The issue is fixed in fast-uri 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of these versions or later. As a workaround, avoid the suffix reference option on untrusted input, or percent-encode a colon in the first path segment of the result before treating it as a URI.",
        "publishedDate": "2026-10-20T07:17:08.937Z",
        "cvssScore": 3.7,
        "cvssSeverity": "LOW",
        "epssPercentile": 0.16037,
        "affectedComponents": [
          "pkg:npm/fast-uri@3.1.8"
        ],
        "source": "OSV"
      },
      {
        "cveId": "CVE-2026-110306",
        "onCISAKev": false,
        "triageStatus": "Not Triaged",
        "description": "fast-uri is a dependency-free RFC 3986 URI parser and serializer for Node.js. In versions before 2.4.8, from 3.0.0 through 3.1.8, and from 4.0.0 through 4.2.2, fast-uri percent-decodes the scheme component with the legacy global unescape() function before validating it, so an input whose decoded scheme is a dangerous token is emitted as a live scheme even though RFC 3986 does not allow percent-encoding in a scheme and no other parser accepts it. An application that screens dangerous schemes on the raw input and then stores or renders the normalized or resolved result can turn an inert string into an executable javascript, data, or vbscript URL, producing a stored or reflected cross-site scripting vector, and the equal() comparison treats an encoded and a plain scheme as the same, which can bypass equality-based allowlists. The issue is fixed in fast-uri 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of these versions or later. As a workaround, reject input whose scheme part contains a percent sign, or check the parsed scheme against an allowlist after normalization and use that same parsed result rather than the raw string.",
        "publishedDate": "2026-10-20T07:17:08.810Z",
        "cvssScore": 6.1,
        "cvssSeverity": "MEDIUM",
        "epssPercentile": 0.09881,
        "affectedComponents": [
          "pkg:npm/fast-uri@3.1.8"
        ],
        "source": "OSV"
      },
      {
        "cveId": "CVE-2026-110180",
        "onCISAKev": false,
        "triageStatus": "Not Triaged",
        "description": "fast-uri is a dependency-free RFC 3986 URI parser and serializer for Node.js. In versions from 2.4.2 through 2.4.7, from 3.1.3 through 3.1.8, and from 4.0.1 through 4.2.2, for HTTP-family schemes the canonicalizeHost() function passes the parsed host to the WHATWG URL parser and adopts its hostname without checking that the parser consumed the entire input as a host, so the authority can be silently rewritten: data before an at-sign is dropped and tab, carriage-return, and line-feed characters are stripped, with no error reported. An application that enforces host-based policy such as denylists, loopback filtering, redirect validation, or outbound proxy routing on one representation can then see the canonical host diverge from what it checked, allowing traffic to be steered to an unintended destination. The issue is fixed in fast-uri 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of these versions or later. As a workaround, reject an authority that contains more than one at-sign or any tab, carriage-return, or line-feed before calling fast-uri, or treat any non-empty parse error as fatal and compare hosts only from the same parse result.",
        "publishedDate": "2026-10-20T07:17:08.687Z",
        "cvssScore": 4.8,
        "cvssSeverity": "MEDIUM",
        "epssPercentile": 0.10411,
        "affectedComponents": [
          "pkg:npm/fast-uri@3.1.8"
        ],
        "source": "OSV"
      },
      {
        "cveId": "CVE-2026-110095",
        "onCISAKev": false,
        "triageStatus": "Not Triaged",
        "description": "fast-uri is a dependency-free RFC 3986 URI parser and serializer for Node.js. In versions before 2.4.8, from 3.0.0 through 3.1.8, and from 4.0.0 through 4.2.2, the normalize() and serialize() functions apply RFC 3986 dot-segment removal to the path of a relative-path reference, even though that algorithm is defined only for the merged target path during resolution, so a leading parent-directory segment can be dropped and a document-relative reference can become root-relative. An application that normalizes an attacker-supplied or user-supplied relative reference and then resolves it, or uses it as a cache, deduplication, or authorization key, can have the reference escape its intended directory and point at a different resource. The issue is fixed in fast-uri 2.4.8, 3.1.9, and 4.2.3, and users should upgrade to one of these versions or later. As a workaround, resolve a relative reference against its absolute base first and normalize the absolute result instead of normalizing the reference beforehand.",
        "publishedDate": "2026-10-20T07:17:08.550Z",
        "cvssScore": 3.7,
        "cvssSeverity": "LOW",
        "epssPercentile": 0.13295,
        "affectedComponents": [
          "pkg:npm/fast-uri@3.1.8"
        ],
        "source": "OSV"
      },
      {
        "cveId": "CVE-2025-66803",
        "onCISAKev": false,
        "triageStatus": "NotAffected",
        "description": "Race condition in the turbo-frame element handler in Hotwired Turbo before 8.0.x causes logout operations to fail when delayed frame responses reapply session cookies after logout. This can be exploited by remote attackers via selective network delays (e.g. delaying requests based on sequence or timing) or by physically proximate attackers when the race condition occurs naturally on shared computers.",
        "publishedDate": "2026-01-20T19:15:49.537Z",
        "cvssScore": 4.8,
        "cvssSeverity": "MEDIUM",
        "epssPercentile": 0.19722,
        "affectedComponents": [
          "pkg:npm/turbo@2.9.16"
        ],
        "justification": "vulnerableCodeNotPresent",
        "scope": "allVersionsOfThisAssetForever",
        "statusNotes": "Justification: CVE-2025-66803 is a Hotwired Turbo Frames cookie race in @hotwired/turbo versions through 8.0.20, fixed in 8.0.21. This repository depends on npm turbo@2.9.16, which is Turborepo, a build CLI. That package has no 8.0.21 release. There is no @hotwired/turbo dependency and no turbo-frame usage in the React apps. A delayed frame response cannot restore a session cookie here because no frame requests are issued. Not affected.",
        "source": "NVD"
      }
    ]
  },
  "metadata": {
    "generatedAt": "2026-10-24T23:33:17.390Z",
    "sourceOrg": "653452b385c6253be38e7721",
    "totalVulnerabilities": 8
  }
}
