OPENSUSE-SU-2026:21557-1

Vulnerability from csaf_opensuse - Published: 2026-08-10 10:55 - Updated: 2026-09-17 17:41
Summary
Security update for gleam
Severity
Moderate
Notes
Title of the patch: Security update for gleam
Description of the patch: This update for gleam fixes the following issues: Changes in gleam: - Update to 1.18.1: * CVE-2026-59247: insufficient verification of data authenticity allows a MITM adversary to substitute forged Hex package contents during dependency resolution (bsc#1272992) * Set minimum required Erlang version to 26 * All features and bug fixes are extensively highlighted with examples in upstream's blog post at https://gleam.run/news/a-field-day-for-gleams-language-server/ and changelog at https://github.com/gleam-lang/gleam/blob/v1.18.1/CHANGELOG.md . Some of the highlights include: - A lot of new features for the LSP - Faster JavaScript using singletons - Deprecation of ambiguous pipe syntax - Path support in Git dependencies - Up to 13% faster compilation - Fixed various bugs in Erlang and JavaScript code generation. - Fixed several bugs in the float handling for the JavaScript target. - Fixed a bug in the generation of Erlang .app files. - Fixed a bug where the formatter would produce invalid code. - Fixed a bug in the TypeScript type definition generation. - Fixed a bug where the compiler would evaluate the numerator and denominator of a division in the wrong order. - Fixed a bug where gleam docs would not be generated.
Patchnames: openSUSE-Leap-16.0-packagehub-471
Terms of use: CSAF 2.0 data is provided by SUSE under the Creative Commons License 4.0 with Attribution (CC-BY-4.0).
CVE-2026-59247
Affected products
Product Identifier Version Remediation
Unresolved product id: openSUSE Leap 16.0:gleam-0:1.18.1-bp160.1.1.aarch64 —
Vendor Fix
Unresolved product id: openSUSE Leap 16.0:gleam-0:1.18.1-bp160.1.1.x86_64 —
Vendor Fix
Threats
Impact moderate
References
To clipboard 

{
  "document": {
    "aggregate_severity": {
      "namespace": "https://www.suse.com/support/security/rating/",
      "text": "moderate"
    },
    "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 gleam",
        "title": "Title of the patch"
      },
      {
        "category": "description",
        "text": "This update for gleam fixes the following issues:\n\nChanges in gleam:\n\n- Update to 1.18.1:\n  * CVE-2026-59247: insufficient verification of data authenticity\n    allows a MITM adversary to substitute forged Hex package\n    contents during dependency resolution (bsc#1272992)\n  * Set minimum required Erlang version to 26\n  * All features and bug fixes are extensively highlighted with\n    examples in upstream\u0027s blog post at\n    https://gleam.run/news/a-field-day-for-gleams-language-server/\n    and changelog at\n    https://github.com/gleam-lang/gleam/blob/v1.18.1/CHANGELOG.md .\n    Some of the highlights include:\n      - A lot of new features for the LSP\n      - Faster JavaScript using singletons\n      - Deprecation of ambiguous pipe syntax\n      - Path support in Git dependencies\n      - Up to 13% faster compilation\n      - Fixed various bugs in Erlang and JavaScript code\n        generation.\n      - Fixed several bugs in the float handling for the JavaScript\n        target.\n      - Fixed a bug in the generation of Erlang .app files.\n      - Fixed a bug where the formatter would produce invalid code.\n      - Fixed a bug in the TypeScript type definition generation.\n      - Fixed a bug where the compiler would evaluate the numerator\n        and denominator of a division in the wrong order.\n      - Fixed a bug where gleam docs would not be generated.\n",
        "title": "Description of the patch"
      },
      {
        "category": "details",
        "text": "openSUSE-Leap-16.0-packagehub-471",
        "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_21557-1.json"
      },
      {
        "category": "self",
        "summary": "SUSE Bug 1272992",
        "url": "https://bugzilla.suse.com/1272992"
      },
      {
        "category": "self",
        "summary": "SUSE CVE CVE-2026-59247 page",
        "url": "https://www.suse.com/security/cve/CVE-2026-59247/"
      }
    ],
    "title": "Security update for gleam",
    "tracking": {
      "current_release_date": "2026-09-17T17:41:38Z",
      "generator": {
        "date": "2026-08-10T10:55:07Z",
        "engine": {
          "name": "cve-database.git:bin/generate-csaf.pl",
          "version": "1"
        }
      },
      "id": "openSUSE-SU-2026:21557-1",
      "initial_release_date": "2026-08-10T10:55:07Z",
      "revision_history": [
        {
          "date": "2026-08-10T10:55:07Z",
          "number": "1",
          "summary": "Current version"
        },
        {
          "date": "2026-09-16T20:44:57Z",
          "number": "2",
          "summary": "unknown changes"
        },
        {
          "date": "2026-09-16T21:46:19Z",
          "number": "3",
          "summary": "unknown changes"
        },
        {
          "date": "2026-09-17T17:41:38Z",
          "number": "4",
          "summary": "unknown changes"
        }
      ],
      "status": "final",
      "version": "4"
    }
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "gleam-0:1.18.1-bp160.1.1.aarch64",
                "product": {
                  "name": "gleam-0:1.18.1-bp160.1.1.aarch64",
                  "product_id": "gleam-0:1.18.1-bp160.1.1.aarch64",
                  "product_identification_helper": {
                    "purl": "pkg:rpm/suse/gleam@1.18.1-bp160.1.1?arch=aarch64"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "aarch64"
          },
          {
            "branches": [
              {
                "category": "product_version",
                "name": "gleam-0:1.18.1-bp160.1.1.x86_64",
                "product": {
                  "name": "gleam-0:1.18.1-bp160.1.1.x86_64",
                  "product_id": "gleam-0:1.18.1-bp160.1.1.x86_64",
                  "product_identification_helper": {
                    "purl": "pkg:rpm/suse/gleam@1.18.1-bp160.1.1?arch=x86_64"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "x86_64"
          },
          {
            "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": "gleam-0:1.18.1-bp160.1.1.aarch64 as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:gleam-0:1.18.1-bp160.1.1.aarch64"
        },
        "product_reference": "gleam-0:1.18.1-bp160.1.1.aarch64",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "gleam-0:1.18.1-bp160.1.1.x86_64 as component of openSUSE Leap 16.0",
          "product_id": "openSUSE Leap 16.0:gleam-0:1.18.1-bp160.1.1.x86_64"
        },
        "product_reference": "gleam-0:1.18.1-bp160.1.1.x86_64",
        "relates_to_product_reference": "openSUSE Leap 16.0"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2026-59247",
      "ids": [
        {
          "system_name": "SUSE CVE Page",
          "text": "https://www.suse.com/security/cve/CVE-2026-59247"
        }
      ],
      "notes": [
        {
          "category": "general",
          "text": "Insufficient Verification of Data Authenticity vulnerability in Gleam allows an adversary in the middle to substitute forged Hex package contents during dependency resolution.\n\nDuring dependency resolution Gleam fetches package metadata from the signature-verified Hex repository, which covers each release\u0027s dependency requirements and SHA-256 outer_checksum. After resolving versions, gleam_cli::dependencies::lookup_package makes a second request to the unsigned Hex API through gleam_core::hex::get_package_release and records the outer_checksum and dependency names from that JSON response into manifest.toml, instead of the values from the verified repository metadata. The Hex repository signature does not cover the API response.\n\nAn adversary in the middle who can intercept TLS with a certificate trusted by the Gleam process (for example a TLS-inspecting proxy using a CA in the operating system trust store or added through GLEAM_CACERTS_PATH), and who can modify both the API release response and the corresponding repository tarball, can supply a package archive with a matching forged checksum without the Hex repository signing key. Gleam verifies the forged tarball against the forged checksum, accepts it, and extracts it as a dependency source, resulting in loss of integrity of the downloaded package contents.\n\nOnly projects that resolve or update Hex dependencies are affected, which happens when the manifest is missing, a dependency is added or updated, or dependency requirements change. Builds that reuse an unchanged, known-good manifest.toml continue to verify tarballs against its pinned checksum. This issue affects gleam: from 0.18.0 before 1.18.0.",
          "title": "CVE description"
        }
      ],
      "product_status": {
        "recommended": [
          "openSUSE Leap 16.0:gleam-0:1.18.1-bp160.1.1.aarch64",
          "openSUSE Leap 16.0:gleam-0:1.18.1-bp160.1.1.x86_64"
        ]
      },
      "references": [
        {
          "category": "external",
          "summary": "CVE-2026-59247",
          "url": "https://www.suse.com/security/cve/CVE-2026-59247"
        },
        {
          "category": "external",
          "summary": "SUSE Bug 1272992 for CVE-2026-59247",
          "url": "https://bugzilla.suse.com/1272992"
        }
      ],
      "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:gleam-0:1.18.1-bp160.1.1.aarch64",
            "openSUSE Leap 16.0:gleam-0:1.18.1-bp160.1.1.x86_64"
          ]
        }
      ],
      "threats": [
        {
          "category": "impact",
          "date": "2026-08-10T10:55:07Z",
          "details": "moderate"
        }
      ],
      "title": "CVE-2026-59247"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





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.



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.