Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ CVE-2026-47192 — kas

🟢 CVSS 2.0 — Low ✅ No Known Exploit CWE-347 NVD
2.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

kas's late signature validation may allow unnoticed repository manipulations

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.

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is high, an attacker needs low-level privileges on the target. A user must be tricked into taking some action. Rated impact: confidentiality low, integrity low, availability low.

CVSS metrics in full

The score comes from this vector: 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

  • Attack vector: Network — reachable from anywhere that can route to the service.
  • Attack complexity: High — the attacker first has to win a race, learn a secret or otherwise prepare the target.
  • Attack requirements: Present — the target has to be in a particular state for the attack to work.
  • Privileges required: Low — an ordinary user account is enough.
  • User interaction: Passive — a victim action is involved, but not a deliberate one.
  • Confidentiality impact: Low — limited, and the attacker does not choose what is affected.
  • Integrity impact: Low — limited, and the attacker does not choose what is affected.
  • Availability impact: Low — limited, and the attacker does not choose what is affected.

Weakness class

CVE-2026-47192 is classified as CWE-347: Improper Verification of Cryptographic Signature. A signature is not checked correctly, so forged or modified content is accepted as genuine.

Affected software

CVE-2026-47192 is recorded against 2 packages.

  • kas (from 4.8 up to 5.3)
  • unknown

Timeline and source

Published on 4 June 2026 and last revised on 15 August 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.

References

github.com (Web)
github.com (Web)
github.com (Web)
github.com (Web)
github.com (Package)

Other advisories for this package

kas has other advisories on record. If you are patching this one, these are worth checking on the same host:

Same weakness in other software

These advisories are the same class of weakness (CWE-347: Improper Verification of Cryptographic Signature) in other software:

CVE-2026-47192 on other distributions

Each distribution ships its own build and its own fixed version. Pick the one you run:

Details

Severity LOW
CVSS Score 2.0
CVSS Vector 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
CWE CWE-347
Public Exploit ✅ No
Source NVD
Published 2026-06-04
Updated 2026-08-20
Modified 2026-08-15
Fix URL N/A

Affected Packages

Software From version Fixed in
kas 4.8 5.3
unknown — —

Similar Threats

Free Vulnerability Check

Is your site affected by CVE-2026-47192?

BotEraser helps you identify potentially vulnerable plugins and themes by checking your installation against CVE-2026-47192 and other known CVE records.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.

Browse related advisories

All advisoriesCVECVE 2026
✓