Storybook is a frontend workshop for building user interface components and pages in isolation. A vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10 relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly) in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including common CI-based builds where secrets are provided via platform environment variables rather than `.env` files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible. Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of this issue and will need to change how they reference environment variables after this update. If a project can no longer read necessary environmental variable values, either prefix the variables with `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either case, do not include sensitive secrets as they will be included in the built bundle.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2025:0978 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2025-68429:
    Storybook is a frontend workshop for building user interface components and pages in isolation. A     vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10     relates to Storybooks handling of environment variables defined in a `.env` file, which could, in     specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by     the `storybook build` command. When a built Storybook is published to the web, the bundles source is     viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be     vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly)     in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built     Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including     common CI-based builds where secrets are provided via platform environment variables rather than `.env`     files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that     share a repo with your Storybook are not affected. Users should upgrade their Storybookon both their     local machines and CI environmentto version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible.
    Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files     and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of     this issue and will need to change how they reference environment variables after this update. If a     project can no longer read necessary environmental variable values, either prefix the variables with     `STORYBOOK_` or use the `env` property in Storybooks configuration to manually specify values. In     either case, do not include sensitive secrets as they will be included in the built bundle.

    CVE-2025-64718:
    js-yaml is a JavaScript YAML parser and dumper. In js-yaml 4.1.0 and below, it's possible for an attacker     to modify the prototype of the result of a parsed yaml document via prototype pollution (`__proto__`). All     users who parse untrusted yaml documents may be impacted. The problem is patched in js-yaml 4.1.1. Users     can protect against this kind of attack on the server by using `node --disable-proto=delete` or `deno` (in     Deno, pollution protection is on by default).

Tenable has extracted the preceding description block directly from the Tencent Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

There are packages installed that are affected by a vulnerability referenced in the following CVE:

  - Storybook is a frontend workshop for building user interface components and pages in isolation. A
    vulnerability present starting in versions 7.0.0 and prior to versions 7.6.21, 8.6.15, 9.1.17, and 10.1.10
    relates to Storybook’s handling of environment variables defined in a `.env` file, which could, in
    specific circumstances, lead to those variables being unexpectedly bundled into the artifacts created by
    the `storybook build` command. When a built Storybook is published to the web, the bundle’s source is
    viewable, thus potentially exposing those variables to anyone with access. For a project to potentially be
    vulnerable to this issue, it must build the Storybook (i.e. run `storybook build` directly or indirectly)
    in a directory that contains a `.env` file (including variants like `.env.local`) and publish the built
    Storybook to the web. Storybooks built without a `.env` file at build time are not affected, including
    common CI-based builds where secrets are provided via platform environment variables rather than `.env`
    files. Storybook runtime environments (i.e. `storybook dev`) are not affected. Deployed applications that
    share a repo with your Storybook are not affected. Users should upgrade their Storybook—on both their
    local machines and CI environment—to version .6.21, 8.6.15, 9.1.17, or 10.1.10 as soon as possible.
    Maintainers additionally recommend that users audit for any sensitive secrets provided via `.env` files
    and rotate those keys. Some projects may have been relying on the undocumented behavior at the heart of
    this issue and will need to change how they reference environment variables after this update. If a
    project can no longer read necessary environmental variable values, either prefix the variables with
    `STORYBOOK_` or use the `env` property in Storybook’s configuration to manually specify values. In either
    case, do not include sensitive secrets as they will be included in the built bundle. (CVE-2025-68429)

ID	Name	Product	Family	Severity
282602	TencentOS Server 4: grafana (TSSA-2025:0978)	Nessus	Tencent Local Security Checks	high
436438	SCA: security update for storybook (GHSA-8452-54wp-rmv6)	Tenable Cloud Security	SCA Checks	medium
436438	SCA: security update for storybook (GHSA-8452-54wp-rmv6)	Tenable Self-Hosted Container Security	SCA Checks	medium

Detections

Analytics

CVE-2025-68429

medium

Tenable Plugins

high

medium

medium