OPENSUSE-SU-2026:21173-1

Vulnerability from csaf_opensuse - Published: 2026-06-29 16:40 - Updated: 2026-09-17 17:37
Summary
Security update for python-pydata-sphinx-theme
Severity
Important
Notes
Title of the patch: Security update for python-pydata-sphinx-theme
Description of the patch: This update for python-pydata-sphinx-theme fixes the following issues: Changes in python-pydata-sphinx-theme: - Refresh js dependencies: * ws to 7.5.11 (bsc#1268957, CVE-2026-48779) - Refresh vendored tarball (CVE-2026-6321, bsc#1264374)
Patchnames: openSUSE-Leap-16.0-packagehub-368
Terms of use: CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
Affected products
Product Identifier Version Remediation
Unresolved product id: openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch —
Vendor Fix
Threats
Impact moderate
Affected products
Recommended 1 product, the same list as for CVE-2026-48779
Threats
Impact important

{
  "document": {
    "aggregate_severity": {
      "namespace": "https://www.suse.com/support/security/rating/",
      "text": "important"
    },
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "Copyright 2024 SUSE LLC. All rights reserved.",
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "summary",
        "text": "Security update for python-pydata-sphinx-theme",
        "title": "Title of the patch"
      },
      {
        "category": "description",
        "text": "This update for python-pydata-sphinx-theme fixes the following issues:\n\nChanges in python-pydata-sphinx-theme:\n\n- Refresh js dependencies:\n  * ws to 7.5.11 (bsc#1268957, CVE-2026-48779)\n\n- Refresh vendored tarball (CVE-2026-6321, bsc#1264374)\n",
        "title": "Description of the patch"
      },
      {
        "category": "details",
        "text": "openSUSE-Leap-16.0-packagehub-368",
        "title": "Patchnames"
      },
      {
        "category": "legal_disclaimer",
        "text": "CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).",
        "title": "Terms of use"
      }
    ],
    "publisher": {
      "category": "vendor",
      "contact_details": "https://www.suse.com/support/security/contact/",
      "name": "SUSE Product Security Team",
      "namespace": "https://www.suse.com/"
    },
    "references": [
      {
        "category": "external",
        "summary": "SUSE ratings",
        "url": "https://www.suse.com/support/security/rating/"
      },
      {
        "category": "self",
        "summary": "URL of this CSAF notice",
        "url": "https://ftp.suse.com/pub/projects/security/csaf/opensuse-su-2026_21173-1.json"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1264374",
        "url": "https://bugzilla.suse.com/1264374"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1268957",
        "url": "https://bugzilla.suse.com/1268957"
      },
      {
        "category": "self",
        "summary": "SUSE CVE CVE-2026-48779 page",
        "url": "https://www.suse.com/security/cve/CVE-2026-48779/"
      },
      {
        "category": "self",
        "summary": "SUSE CVE CVE-2026-6321 page",
        "url": "https://www.suse.com/security/cve/CVE-2026-6321/"
      }
    ],
    "title": "Security update for python-pydata-sphinx-theme",
    "tracking": {
      "current_release_date": "2026-09-17T17:37:10Z",
      "generator": {
        "date": "2026-06-29T16:40:20Z",
        "engine": {
          "name": "cve-database.git:bin/generate-csaf.pl",
          "version": "1"
        }
      },
      "id": "openSUSE-SU-2026:21173-1",
      "initial_release_date": "2026-06-29T16:40:20Z",
      "revision_history": [
        {
          "date": "2026-06-29T16:40:20Z",
          "number": "1",
          "summary": "Current version"
        },
        {
          "date": "2026-09-16T20:40:16Z",
          "number": "2",
          "summary": "unknown changes"
        },
        {
          "date": "2026-09-16T21:42:17Z",
          "number": "3",
          "summary": "unknown changes"
        },
        {
          "date": "2026-09-17T17:37:10Z",
          "number": "4",
          "summary": "unknown changes"
        }
      ],
      "status": "final",
      "version": "4"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch",
                "product": {
                  "name": "python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch",
                  "product_id": "python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch",
                  "product_identification_helper": {
                    "purl": "pkg:rpm/suse/python313-pydata-sphinx-theme@0.16.1-bp160.2.1?arch=noarch"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "noarch"
          },
          {
            "branches": [
              {
                "category": "product_name",
                "name": "openSUSE Leap 16.0",
                "product": {
                  "name": "openSUSE Leap 16.0",
                  "product_id": "openSUSE Leap 16.0"
                }
              }
            ],
            "category": "product_family",
            "name": "SUSE Linux Enterprise"
          }
        ],
        "category": "vendor",
        "name": "SUSE"
      }
    ],
    "relationships": [
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch"
        },
        "product_reference": "python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2026-48779",
      "ids": [
        {
          "system_name": "SUSE CVE Page",
          "text": "https://www.suse.com/security/cve/CVE-2026-48779"
        }
      ],
      "notes": [
        {
          "category": "general",
          "text": "ws is an open source WebSocket client and server for Node.js. All versions from 1.1.0 up to (but not including) 5.2.5, from 6.0.0 up to 6.2.4, from 7.0.0 up to 7.5.11, and from 8.0.0 up to 8.21.0 are affected by a memory exhaustion DoS vulnerability. A peer can send a high volume of exceptionally small fragments and data chunks, with modest network traffic, to force the remote peer into allocating and holding structural wrappers that consume far more memory than the default documented message-size limit, leading to process termination due to OOM. This issue has been fixed in versions 5.2.5, 6.2.4, 7.5.11, and 8.21.0.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "recommended": [
          "openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "CVE-2026-48779",
          "url": "https://www.suse.com/security/cve/CVE-2026-48779"
        },
        {
          "category": "external",
          "summary": "SUSE Bug 1268904 for CVE-2026-48779",
          "url": "https://bugzilla.suse.com/1268904"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
          "product_ids": [
            "openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "baseScore": 6.5,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
            "version": "3.1"
          },
          "products": [
            "openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "date": "2026-06-29T16:40:20Z",
          "details": "moderate"
        }
      ],
      "title": "CVE-2026-48779"
    },
    {
      "cve": "CVE-2026-6321",
      "ids": [
        {
          "system_name": "SUSE CVE Page",
          "text": "https://www.suse.com/security/cve/CVE-2026-6321"
        }
      ],
      "notes": [
        {
          "category": "general",
          "text": "fast-uri decoded percent-encoded path separators and dot segments before applying dot-segment removal in its normalize() and equal() functions. Encoded path data was treated like real slashes and parent-directory references, so distinct URIs could collapse onto the same normalized path. Applications that normalize or compare attacker-controlled URLs to enforce path-based policy can be bypassed, with a path that appears confined under an allowed prefix normalizing to a different location. Versions \u003c= 3.1.0 are affected. Update to 3.1.1 or later.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "recommended": [
          "openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "CVE-2026-6321",
          "url": "https://www.suse.com/security/cve/CVE-2026-6321"
        },
        {
          "category": "external",
          "summary": "SUSE Bug 1264367 for CVE-2026-6321",
          "url": "https://bugzilla.suse.com/1264367"
        }
      ],
      "remediations": [
        {
          "category": "vendor_fix",
          "details": "To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or \"zypper patch\".\n",
          "product_ids": [
            "openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch"
          ]
        }
      ],
      "scores": [
        {
          "cvss_v3": {
            "baseScore": 7.5,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
            "version": "3.1"
          },
          "products": [
            "openSUSE Leap 16.0:python313-pydata-sphinx-theme-0:0.16.1-bp160.2.1.noarch"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "date": "2026-06-29T16:40:20Z",
          "details": "important"
        }
      ],
      "title": "CVE-2026-6321"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.