CLEANSTART-2026-FN73056: json-smart through 2

Published Nov 13, 2026
·
Updated

CVE-2026-113602 affects multiple packages. json-smart through 2. See references for individual vulnerability details.

Affected Software

9 affected componentsFixes available
cleanstart/trino<484-r2
484-r2
cleanstart/wso2mi<4.3.0-r1
4.3.0-r1
cleanstart/wso2mi<4.4.0-r1
4.4.0-r1
cleanstart/wso2mi<4.5.0-r1
4.5.0-r1
cleanstart/wso2am<4.7.0-r5
4.7.0-r5
cleanstart/rundeck<6.0.1-r11
6.0.1-r11
cleanstart/rundeck<6.1.0-r6
6.1.0-r6
cleanstart/wso2mi<4.6.0-r11
4.6.0-r11
cleanstart/strimzi-kafka-operator<0.51.0-r8
0.51.0-r8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade cleanstart/trino to a version that resolves this vulnerability.

    Fixed in 484-r2
  2. Upgrade

    Upgrade cleanstart/wso2mi to a version that resolves this vulnerability.

    Fixed in 4.3.0-r1
  3. Upgrade

    Upgrade cleanstart/wso2mi to a version that resolves this vulnerability.

    Fixed in 4.4.0-r1
  4. Upgrade

    Upgrade cleanstart/wso2mi to a version that resolves this vulnerability.

    Fixed in 4.5.0-r1
  5. Upgrade

    Upgrade cleanstart/wso2am to a version that resolves this vulnerability.

    Fixed in 4.7.0-r5
  6. Upgrade

    Upgrade cleanstart/rundeck to a version that resolves this vulnerability.

    Fixed in 6.0.1-r11
  7. Upgrade

    Upgrade cleanstart/rundeck to a version that resolves this vulnerability.

    Fixed in 6.1.0-r6
  8. Upgrade

    Upgrade cleanstart/wso2mi to a version that resolves this vulnerability.

    Fixed in 4.6.0-r11
  9. Upgrade

    Upgrade cleanstart/strimzi-kafka-operator to a version that resolves this vulnerability.

    Fixed in 0.51.0-r8

Event History

Nov 13, 2026
Advisory Published
via OSV·12:37 AM
Data Sourced
via OSV·12:37 AM
DescriptionSeverityAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which Cleanstart packages are listed as affected?

The listed packages are cleanstart/wso2mi, cleanstart/rundeck, cleanstart/trino, cleanstart/wso2am, and cleanstart/strimzi-kafka-operator.

2

What does the supplied severity vector indicate about exploitation requirements?

The vector indicates network-reachable exploitation with low attack complexity. It indicates no privileges or user interaction are required.

3

What impact is indicated by the supplied severity vector?

The vector indicates a low integrity impact. It indicates no confidentiality or availability impact, and the scope is unchanged.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203