CVE-2026-47192: Kas Kas's Late Signature Validation May Vulnerability

LOW
Advisory Identifier: GHSA-4vqc-wpwg-vh7j
CWE-347
Published
Advisory Summary

CVE-2026-47192 is a LOW kas's late signature validation may vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Kas libraries in the PyPI ecosystem. The issue involves kas's late signature validation may allow unnoticed repository manipulations. Remediation is available by upgrading affected packages to version 5.3.

CVE-2026-47192 at a Glance

CVE Identifier CVE-2026-47192
GHSA Identifier GHSA-4vqc-wpwg-vh7j
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Kas
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix CVE-2026-47192

To remediate this vulnerability, upgrade all affected Kas dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

kas fixed: 5.3
pip install kas>=5.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

pip show kas

How to Check if You Are Affected

To determine whether your Python environment is affected by CVE-2026-47192, inspect your installed packages using pip:

pip show kas

Analyze the terminal output to locate any version of Kas in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.3), your application is affected.

Note: The pip show kas command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Kas, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact So far, kas checks out and processes repositories regarding configuration includes prior to validating signatures of those repositories. This may allow to replace on original repository with one under the control of an attacker under very specific conditions. First of all, the attacker must have gained control of a repository that a kas file of the victim is referencing. Furthermore, the following conditions must be fulfilled: - the victim's kas configuration must include a configuration file from the attacked repository - the repository state is referenced by tag, and no commit ID is specified (this is triggering a warning, though) - the key used for validating the tag or commit signature is stored as file in a repository - no fingerprint for the key is specified - the `_source_dir` key must not be set by the victim when calling kas (e.g. by avoiding a local `.config.yaml`) Given these conditions, the attacker could modify the included kas configuration in way that the key used to validate the tag signature of the attacker's repository could be replaced by an attacker-chosen key. No other exploit possibilities have been identified so far, but this does not rule out that those may exist. ### Patches The vulnerability was introduced with a2480fe59b6421eb96cf3bd86527ae6e412a331e, commit https://github.com/siemens/kas/commit/5b2114becfc154b16ef496d24f8c2191a2297f57 is resolving this issue. A misuse of `_source_dir` is resolved by commit https://github.com/siemens/kas/commit/c443c0a1fd0f9bd6a689a44d95a252085fc6da88. Shadowing a commit by a branch of the same name is described in advisory https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r and is addressed by commit https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5. All patches have been released along with kas version 5.3. ### Workarounds Pin the expected signature key via its fingerprint, also when storing it as file in a repository.

CVE-2026-47192 Affected Kas Versions

1 component(s)
Fixed Versions:
5.3
Product / Package Ecosystem Affected Versions Fixed Version
kas
PyPI
≥ 4.8
< 5.3
5.3

References

Frequently Asked Questions

What is CVE-2026-47192?
CVE-2026-47192 is a security vulnerability in Kas involving kas's late signature validation may allow unnoticed repository manipulations under CWE-347: Improper Verification of Cryptographic Signature.
Which Kas versions are affected?
Affected versions include releases prior to 5.3 across affected packages: kas.
What version fixes CVE-2026-47192?
Upgrading to 5.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is kas affected?
Yes, kas is affected in releases prior to 5.3. Upgrade your dependency to 5.3 or later.
What CWE is associated with CVE-2026-47192?
CVE-2026-47192 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check PyPI dependencies for CVE-2026-47192?
Run the dependency tree command: 'pip show kas'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-4vqc-wpwg-vh7j",
  "modified" : "2026-06-04T17:36:03Z",
  "published" : "2026-06-04T17:36:03Z",
  "aliases" : [ "CVE-2026-47192" ],
  "summary" : "kas's late signature validation may allow unnoticed repository manipulations",
  "details" : "### Impact\nSo far, kas checks out and processes repositories regarding configuration includes prior to validating signatures of those repositories. This may allow to replace on original repository with one under the control of an attacker under very specific conditions.\n\nFirst of all, the attacker must have gained control of a repository that a kas file of the victim is referencing. Furthermore, the following conditions must be fulfilled:\n - the victim's kas configuration must include a configuration file from the attacked repository\n - the repository state is referenced by tag, and no commit ID is specified (this is triggering a warning, though)\n - the key used for validating the tag or commit signature is stored as file in a repository\n - no fingerprint for the key is specified\n - the  `_source_dir` key must not be set by the victim when calling kas (e.g. by avoiding a local `.config.yaml`)\n\nGiven these conditions, the attacker could modify the included kas configuration in way that the key used to validate the tag signature of the attacker's repository could be replaced by an attacker-chosen key.\n\nNo other exploit possibilities have been identified so far, but this does not rule out that those may exist.\n\n### Patches\nThe vulnerability was introduced with a2480fe59b6421eb96cf3bd86527ae6e412a331e, commit https://github.com/siemens/kas/commit/5b2114becfc154b16ef496d24f8c2191a2297f57 is resolving this issue. A misuse of `_source_dir` is resolved by commit https://github.com/siemens/kas/commit/c443c0a1fd0f9bd6a689a44d95a252085fc6da88. Shadowing a commit by a branch of the same name is described in advisory https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r and is addressed by commit https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5. All patches have been released along with kas version 5.3.\n\n### Workarounds\nPin the expected signature key via its fingerprint, also when storing it as file in a repository.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "kas"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.8"
      }, {
        "fixed" : "5.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/siemens/kas/security/advisories/GHSA-4vqc-wpwg-vh7j"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/siemens/kas/security/advisories/GHSA-qjwp-hrq6-r26r"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/siemens/kas/commit/4cb4a3d01122ffaec9feaae768a5814092f6f9b5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/siemens/kas/commit/5b2114becfc154b16ef496d24f8c2191a2297f57"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/siemens/kas"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-06-04T17:36:03Z",
    "nvd_published_at" : null
  }
}