Repository scan
openg2p-deployment
OpenG2P/openg2p-deployment · branch main · scanned 1 Jun 2026
High 630
High 117 known vulnerabilities in stdlib@1.14.15 (openg2p/simple-mpesa:v0.1-alpha)
How to fix
Update stdlib from 1.14.15 to 1.15.13 or later in openg2p/simple-mpesa:v0.1-alpha. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.15.13); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2021-33195 fixed in 1.15.13
- High CVE-2023-24539 fixed in 1.19.9
- High CVE-2023-29400 fixed in 1.19.9
- High CVE-2021-27918 fixed in 1.15.9
- High CVE-2021-33196 fixed in 1.15.13
- High CVE-2021-33198 fixed in 1.15.13
- High CVE-2021-39293 fixed in 1.16.8
- High CVE-2021-41771 fixed in 1.16.10
- High CVE-2021-41772 fixed in 1.16.10
- High CVE-2021-44716 fixed in 1.16.12
- High CVE-2022-23772 fixed in 1.16.14
- High CVE-2022-24675 fixed in 1.17.9
- High CVE-2022-24921 fixed in 1.16.15
- High CVE-2022-27664 fixed in 1.18.6
- High CVE-2022-28131 fixed in 1.17.12
- High CVE-2022-28327 fixed in 1.17.9
- High CVE-2022-2879 fixed in 1.18.7
- High CVE-2022-2880 fixed in 1.18.7
- High CVE-2022-29804 fixed in 1.17.11
- High CVE-2022-30630 fixed in 1.17.12
- and 97 more
High 39 known vulnerabilities in openssl@3.0.7-r0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update openssl from 3.0.7-r0 to 3.0.8-r0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.8-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-0286 fixed in 3.0.8-r0
- High CVE-2025-69419 fixed in 3.0.19-r0
- High CVE-2022-3996 fixed in 3.0.7-r2
- High CVE-2023-0464 fixed in 3.0.8-r1
- High CVE-2023-5363 fixed in 3.0.12-r0
- High CVE-2024-4741 fixed in 3.0.14-r0
- High CVE-2024-6119 fixed in 3.0.15-r0
- High CVE-2025-69420 fixed in 3.0.19-r0
- High CVE-2025-69421 fixed in 3.0.19-r0
- High CVE-2025-9230 fixed in 3.0.19-r0
- High CVE-2025-15467 fixed in 3.0.19-r0
- High CVE-2024-5535 fixed in 3.0.14-r0
- Medium CVE-2022-4203 fixed in 3.0.8-r0
- Medium CVE-2022-4304 fixed in 3.0.8-r0
- Medium CVE-2022-4450 fixed in 3.0.8-r0
- Medium CVE-2023-0215 fixed in 3.0.8-r0
- Medium CVE-2023-0216 fixed in 3.0.8-r0
- Medium CVE-2023-0217 fixed in 3.0.8-r0
- Medium CVE-2023-0401 fixed in 3.0.8-r0
- Medium CVE-2025-69418 fixed in 3.0.19-r0
- and 19 more
High 39 known vulnerabilities in openssl@3.0.7-r0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update openssl from 3.0.7-r0 to 3.0.8-r0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.8-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-0286 fixed in 3.0.8-r0
- High CVE-2025-69419 fixed in 3.0.19-r0
- High CVE-2022-3996 fixed in 3.0.7-r2
- High CVE-2023-0464 fixed in 3.0.8-r1
- High CVE-2023-5363 fixed in 3.0.12-r0
- High CVE-2024-4741 fixed in 3.0.14-r0
- High CVE-2024-6119 fixed in 3.0.15-r0
- High CVE-2025-69420 fixed in 3.0.19-r0
- High CVE-2025-69421 fixed in 3.0.19-r0
- High CVE-2025-9230 fixed in 3.0.19-r0
- High CVE-2025-15467 fixed in 3.0.19-r0
- High CVE-2024-5535 fixed in 3.0.14-r0
- Medium CVE-2022-4203 fixed in 3.0.8-r0
- Medium CVE-2022-4304 fixed in 3.0.8-r0
- Medium CVE-2022-4450 fixed in 3.0.8-r0
- Medium CVE-2023-0215 fixed in 3.0.8-r0
- Medium CVE-2023-0216 fixed in 3.0.8-r0
- Medium CVE-2023-0217 fixed in 3.0.8-r0
- Medium CVE-2023-0401 fixed in 3.0.8-r0
- Medium CVE-2025-69418 fixed in 3.0.19-r0
- and 19 more
High 38 known vulnerabilities in axios@0.26.1 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update axios from 0.26.1 to 0.31.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.31.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-44495 fixed in 0.31.1
- High CVE-2026-44495 fixed in 0.31.1
- High CVE-2026-42043 fixed in 0.31.1
- High CVE-2026-42043 fixed in 0.31.1
- High CVE-2026-42033 fixed in 0.31.1
- High CVE-2026-42033 fixed in 0.31.1
- High CVE-2026-42035 fixed in 0.31.1
- High CVE-2026-42035 fixed in 0.31.1
- High CVE-2025-58754 fixed in 1.12.0,
- High CVE-2025-58754 fixed in 1.12.0,
- High CVE-2026-25639 fixed in 1.13.5
- High CVE-2026-25639 fixed in 1.13.5
- High CVE-2025-27152 fixed in 1.8.2
- High CVE-2025-27152 fixed in 1.8.2
- High CVE-2026-44492 fixed in 0.32.0
- High CVE-2026-44492 fixed in 0.32.0
- Medium CVE-2026-40175 fixed in 0.31.0
- Medium CVE-2026-40175 fixed in 0.31.0
- Medium CVE-2026-42041 fixed in 0.31.1
- Medium CVE-2026-42041 fixed in 0.31.1
- and 18 more
High 38 known vulnerabilities in axios@0.25.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update axios from 0.25.0 to 0.31.1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.31.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-44495 fixed in 0.31.1
- High CVE-2026-44495 fixed in 0.31.1
- High CVE-2026-42043 fixed in 0.31.1
- High CVE-2026-42043 fixed in 0.31.1
- High CVE-2026-42033 fixed in 0.31.1
- High CVE-2026-42033 fixed in 0.31.1
- High CVE-2026-42035 fixed in 0.31.1
- High CVE-2026-42035 fixed in 0.31.1
- High CVE-2025-58754 fixed in 1.12.0,
- High CVE-2025-58754 fixed in 1.12.0,
- High CVE-2026-25639 fixed in 1.13.5
- High CVE-2026-25639 fixed in 1.13.5
- High CVE-2025-27152 fixed in 1.8.2
- High CVE-2025-27152 fixed in 1.8.2
- High CVE-2026-44492 fixed in 0.32.0
- High CVE-2026-44492 fixed in 0.32.0
- Medium CVE-2026-40175 fixed in 0.31.0
- Medium CVE-2026-40175 fixed in 0.31.0
- Medium CVE-2026-42041 fixed in 0.31.1
- Medium CVE-2026-42041 fixed in 0.31.1
- and 18 more
High 28 known vulnerabilities in curl@7.87.0-r0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update curl from 7.87.0-r0 to 8.1.0-r0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.1.0-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-28319 fixed in 8.1.0-r0
- High CVE-2023-38039 fixed in 8.3.0-r0
- High CVE-2024-6197 fixed in 8.9.0-r0
- High CVE-2024-2398 fixed in 8.7.1-r0
- High CVE-2023-27533 fixed in 7.88.1-r1
- High CVE-2023-27534 fixed in 7.88.1-r1
- High CVE-2023-38545 fixed in 8.4.0-r0
- Medium CVE-2023-23916 fixed in 7.87.0-r2
- Medium CVE-2024-6874 fixed in 8.9.0-r0
- Medium CVE-2023-46219 fixed in 8.5.0-r0
- Medium CVE-2024-0853 fixed in no fix yet
- Medium CVE-2023-27538 fixed in 7.88.1-r1
- Medium CVE-2023-27535 fixed in 7.88.1-r1
- Medium CVE-2023-27536 fixed in 7.88.1-r1
- Medium CVE-2023-27537 fixed in 7.88.1-r1
- Medium CVE-2023-28320 fixed in 8.1.0-r0
- Medium CVE-2023-28321 fixed in 8.1.0-r0
- Medium CVE-2024-2379 fixed in 8.7.1-r0
- Medium CVE-2023-46218 fixed in 8.5.0-r0
- Medium CVE-2024-2466 fixed in 8.7.1-r0
- and 8 more
High 28 known vulnerabilities in curl@7.87.0-r0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update curl from 7.87.0-r0 to 8.1.0-r0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.1.0-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-28319 fixed in 8.1.0-r0
- High CVE-2023-38039 fixed in 8.3.0-r0
- High CVE-2024-6197 fixed in 8.9.0-r0
- High CVE-2024-2398 fixed in 8.7.1-r0
- High CVE-2023-27533 fixed in 7.88.1-r1
- High CVE-2023-27534 fixed in 7.88.1-r1
- High CVE-2023-38545 fixed in 8.4.0-r0
- Medium CVE-2023-23916 fixed in 7.87.0-r2
- Medium CVE-2024-6874 fixed in 8.9.0-r0
- Medium CVE-2023-46219 fixed in 8.5.0-r0
- Medium CVE-2024-0853 fixed in no fix yet
- Medium CVE-2023-27538 fixed in 7.88.1-r1
- Medium CVE-2023-27535 fixed in 7.88.1-r1
- Medium CVE-2023-27536 fixed in 7.88.1-r1
- Medium CVE-2023-27537 fixed in 7.88.1-r1
- Medium CVE-2023-28320 fixed in 8.1.0-r0
- Medium CVE-2023-28321 fixed in 8.1.0-r0
- Medium CVE-2024-2379 fixed in 8.7.1-r0
- Medium CVE-2023-46218 fixed in 8.5.0-r0
- Medium CVE-2024-2466 fixed in 8.7.1-r0
- and 8 more
High 23 known vulnerabilities in crypto@0.0.0-20200622213623-75b288015ac9 (openg2p/simple-mpesa:v0.1-alpha)
How to fix
Update crypto from 0.0.0-20200622213623-75b288015ac9 to 0.0.0-20201216223049-8b5274cf687f or later in openg2p/simple-mpesa:v0.1-alpha. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.0.0-20201216223049-8b5274cf687f); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2020-29652 fixed in 0.0.0-20201216223049-8b5274cf687f
- High CVE-2021-43565 fixed in 0.0.0-20211202192323-5770296d904e
- High CVE-2022-27191 fixed in 0.0.0-20220314234659-1baeb1ce4c0b
- High CVE-2022-30636 fixed in 0.0.0-20220525230936-793ad666bf5e
- High CVE-2025-22869 fixed in 0.35.0
- High CVE-2025-47913 fixed in 0.43.0
- High CVE-2026-39829 fixed in 0.52.0
- High CVE-2026-46597 fixed in 0.52.0
- High CVE-2024-45337 fixed in 0.31.0
- High CVE-2026-39830 fixed in 0.52.0
- High CVE-2026-39831 fixed in 0.52.0
- High CVE-2026-39832 fixed in 0.52.0
- High CVE-2026-39833 fixed in 0.52.0
- High CVE-2026-39834 fixed in 0.52.0
- High CVE-2026-42508 fixed in 0.52.0
- High CVE-2026-46595 fixed in 0.52.0
- Medium CVE-2025-47914 fixed in 0.45.0
- Medium CVE-2025-58181 fixed in 0.45.0
- Medium CVE-2026-39835 fixed in 0.52.0
- Medium CVE-2026-46598 fixed in 0.52.0
- and 3 more
High 21 known vulnerabilities in protobufjs@6.11.2 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update protobufjs from 6.11.2 to 6.11.3 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.11.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-25878 fixed in 6.11.3
- High CVE-2022-25878 fixed in 6.11.3
- High CVE-2026-44289 fixed in 7.5.6
- High CVE-2026-44289 fixed in 7.5.6
- High CVE-2026-44290 fixed in 7.5.6
- High CVE-2026-44290 fixed in 7.5.6
- High CVE-2026-44293 fixed in 7.5.6
- High CVE-2026-44293 fixed in 7.5.6
- High CVE-2026-44291 fixed in 7.5.6
- High CVE-2026-44291 fixed in 7.5.6
- High CVE-2026-41242 fixed in 7.5.5
- High CVE-2026-41242 fixed in 7.5.5
- High CVE-2023-36665 fixed in 6.11.4
- Medium CVE-2026-44288 fixed in 7.5.6
- Medium CVE-2026-44288 fixed in 7.5.6
- Medium CVE-2026-44292 fixed in 7.5.6
- Medium CVE-2026-44292 fixed in 7.5.6
- Medium CVE-2026-44294 fixed in 7.5.6
- Medium CVE-2026-44294 fixed in 7.5.6
- Medium CVE-2026-45740 fixed in 7.5.8
- and 1 more
High 21 known vulnerabilities in protobufjs@6.11.2 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update protobufjs from 6.11.2 to 6.11.3 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.11.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-25878 fixed in 6.11.3
- High CVE-2022-25878 fixed in 6.11.3
- High CVE-2026-44289 fixed in 7.5.6
- High CVE-2026-44289 fixed in 7.5.6
- High CVE-2026-44290 fixed in 7.5.6
- High CVE-2026-44290 fixed in 7.5.6
- High CVE-2026-44293 fixed in 7.5.6
- High CVE-2026-44293 fixed in 7.5.6
- High CVE-2026-44291 fixed in 7.5.6
- High CVE-2026-44291 fixed in 7.5.6
- High CVE-2026-41242 fixed in 7.5.5
- High CVE-2026-41242 fixed in 7.5.5
- High CVE-2023-36665 fixed in 6.11.4
- Medium CVE-2026-44288 fixed in 7.5.6
- Medium CVE-2026-44288 fixed in 7.5.6
- Medium CVE-2026-44292 fixed in 7.5.6
- Medium CVE-2026-44292 fixed in 7.5.6
- Medium CVE-2026-44294 fixed in 7.5.6
- Medium CVE-2026-44294 fixed in 7.5.6
- Medium CVE-2026-45740 fixed in 7.5.8
- and 1 more
High 13 known vulnerabilities in v2@2.0.2 (openg2p/simple-mpesa:v0.1-alpha)
How to fix
No fixed version of v2 is available yet. Check whether openg2p/simple-mpesa:v0.1-alpha needs v2 at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2026-32286 fixed in no fix yet
- High GHSA-7jwh-3vrq-q3m8 fixed in 2.3.3
- High CVE-2025-54801 fixed in 2.52.9
- High CVE-2023-45141 fixed in 2.50.0
- High CVE-2025-66630 fixed in 2.52.11
- High CVE-2024-25124 fixed in 2.52.1
- High CVE-2023-45128 fixed in 2.50.0
- High CVE-2024-27304 fixed in 2.3.3
- High CVE-2024-38513 fixed in 2.52.5
- Medium CVE-2023-41338 fixed in 2.49.2
- Medium CVE-2026-42554 fixed in 2.52.13
- Medium CVE-2018-20744 fixed in 2.43.0
- Medium CVE-2026-25882 fixed in 2.52.12
High 12 known vulnerabilities in binutils@2.39-r2 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
No fixed version of binutils is available yet. Check whether lalithkota/sp-con-payment-manager-core-connector:develop needs binutils at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2022-44840 fixed in no fix yet
- High CVE-2022-45703 fixed in no fix yet
- High CVE-2022-47673 fixed in no fix yet
- High CVE-2022-47695 fixed in no fix yet
- High CVE-2022-47696 fixed in no fix yet
- High CVE-2023-1579 fixed in no fix yet
- Medium CVE-2022-4285 fixed in no fix yet
- Medium CVE-2022-48063 fixed in no fix yet
- Medium CVE-2022-48064 fixed in no fix yet
- Medium CVE-2022-48065 fixed in no fix yet
- Medium CVE-2023-25584 fixed in no fix yet
- Medium CVE-2023-1972 fixed in no fix yet
High 12 known vulnerabilities in git@2.38.2-r0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update git from 2.38.2-r0 to 2.38.5-r0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.38.5-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-29007 fixed in 2.38.5-r0
- High CVE-2024-32465 fixed in 2.39.5-r0
- High CVE-2023-25652 fixed in 2.38.5-r0
- High CVE-2024-32004 fixed in 2.39.5-r0
- High CVE-2024-32002 fixed in 2.39.5-r0
- High CVE-2022-23521 fixed in 2.38.3-r0
- High CVE-2022-41903 fixed in 2.38.3-r0
- Medium CVE-2023-22490 fixed in 2.38.4-r0
- Medium CVE-2023-23946 fixed in 2.38.4-r0
- Low CVE-2023-25815 fixed in 2.38.5-r0
- Low CVE-2024-32020 fixed in 2.39.5-r0
- Low CVE-2024-32021 fixed in 2.39.5-r0
High 12 known vulnerabilities in binutils@2.39-r2 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
No fixed version of binutils is available yet. Check whether lalithkota/sp-con-payments-interop-layer:develop needs binutils at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- High CVE-2022-44840 fixed in no fix yet
- High CVE-2022-45703 fixed in no fix yet
- High CVE-2022-47673 fixed in no fix yet
- High CVE-2022-47695 fixed in no fix yet
- High CVE-2022-47696 fixed in no fix yet
- High CVE-2023-1579 fixed in no fix yet
- Medium CVE-2022-4285 fixed in no fix yet
- Medium CVE-2022-48063 fixed in no fix yet
- Medium CVE-2022-48064 fixed in no fix yet
- Medium CVE-2022-48065 fixed in no fix yet
- Medium CVE-2023-25584 fixed in no fix yet
- Medium CVE-2023-1972 fixed in no fix yet
High 12 known vulnerabilities in git@2.38.2-r0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update git from 2.38.2-r0 to 2.38.5-r0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.38.5-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-29007 fixed in 2.38.5-r0
- High CVE-2024-32465 fixed in 2.39.5-r0
- High CVE-2023-25652 fixed in 2.38.5-r0
- High CVE-2024-32004 fixed in 2.39.5-r0
- High CVE-2024-32002 fixed in 2.39.5-r0
- High CVE-2022-23521 fixed in 2.38.3-r0
- High CVE-2022-41903 fixed in 2.38.3-r0
- Medium CVE-2023-22490 fixed in 2.38.4-r0
- Medium CVE-2023-23946 fixed in 2.38.4-r0
- Low CVE-2023-25815 fixed in 2.38.5-r0
- Low CVE-2024-32020 fixed in 2.39.5-r0
- Low CVE-2024-32021 fixed in 2.39.5-r0
High 12 known vulnerabilities in openssl@3.1.2-r0 (openg2p/simple-mpesa:v0.1-alpha)
How to fix
Update openssl from 3.1.2-r0 to 3.1.4-r0 or later in openg2p/simple-mpesa:v0.1-alpha. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.1.4-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-5363 fixed in 3.1.4-r0
- High CVE-2024-4741 fixed in 3.1.6-r0
- High CVE-2024-6119 fixed in 3.1.7-r0
- High CVE-2024-5535 fixed in 3.1.6-r0
- Medium CVE-2024-13176 fixed in 3.1.8-r0
- Medium CVE-2024-9143 fixed in 3.1.7-r1
- Medium CVE-2023-5678 fixed in 3.1.4-r1
- Medium CVE-2024-4603 fixed in 3.1.5-r0
- Medium CVE-2024-0727 fixed in 3.1.4-r5
- Medium CVE-2023-6237 fixed in 3.1.4-r4
- Medium CVE-2024-2511 fixed in 3.1.4-r6
- Medium CVE-2023-6129 fixed in 3.1.4-r3
High 10 known vulnerabilities in minimatch@3.0.4 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update minimatch from 3.0.4 to 3.0.5 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-3517 fixed in 3.0.5
- High CVE-2026-27903 fixed in 5.1.8
- High CVE-2026-27903 fixed in 3.1.3
- High CVE-2026-27903 fixed in 3.1.3
- High CVE-2026-27904 fixed in 5.1.8
- High CVE-2026-27904 fixed in 3.1.4
- High CVE-2026-27904 fixed in 3.1.4
- High CVE-2026-26996 fixed in 10.2.1
- High CVE-2026-26996 fixed in 10.2.1
- High CVE-2026-26996 fixed in 10.2.1
High 10 known vulnerabilities in minimatch@3.0.4 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update minimatch from 3.0.4 to 3.0.5 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-3517 fixed in 3.0.5
- High CVE-2026-27903 fixed in 5.1.8
- High CVE-2026-27903 fixed in 3.1.3
- High CVE-2026-27903 fixed in 3.1.3
- High CVE-2026-27904 fixed in 3.1.4
- High CVE-2026-27904 fixed in 3.1.4
- High CVE-2026-27904 fixed in 5.1.8
- High CVE-2026-26996 fixed in 10.2.1
- High CVE-2026-26996 fixed in 10.2.1
- High CVE-2026-26996 fixed in 10.2.1
High 9 known vulnerabilities in python3@3.10.9-r1 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update python3 from 3.10.9-r1 to 3.10.15-r0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.10.15-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-4032 fixed in 3.10.15-r0
- High CVE-2024-6232 fixed in 3.10.15-r0
- High CVE-2024-7592 fixed in 3.10.15-r0
- High CVE-2023-6597 fixed in 3.10.14-r0
- High CVE-2024-8088 fixed in 3.10.14-r2
- Medium CVE-2023-27043 fixed in 3.10.15-r0
- Medium CVE-2023-40217 fixed in 3.10.13-r0
- Medium CVE-2024-6923 fixed in 3.10.15-r0
- Medium CVE-2024-0450 fixed in 3.10.14-r0
High 9 known vulnerabilities in python3@3.10.9-r1 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update python3 from 3.10.9-r1 to 3.10.15-r0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.10.15-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-4032 fixed in 3.10.15-r0
- High CVE-2024-6232 fixed in 3.10.15-r0
- High CVE-2024-7592 fixed in 3.10.15-r0
- High CVE-2023-6597 fixed in 3.10.14-r0
- High CVE-2024-8088 fixed in 3.10.14-r2
- Medium CVE-2023-27043 fixed in 3.10.15-r0
- Medium CVE-2023-40217 fixed in 3.10.13-r0
- Medium CVE-2024-6923 fixed in 3.10.15-r0
- Medium CVE-2024-0450 fixed in 3.10.14-r0
High 7 known vulnerabilities in expat@2.5.0-r0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update expat from 2.5.0-r0 to 2.6.0-r0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.6.0-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-52425 fixed in 2.6.0-r0
- High CVE-2024-28757 fixed in 2.6.2-r0
- High CVE-2024-45490 fixed in 2.6.3-r0
- High CVE-2024-45491 fixed in 2.6.3-r0
- High CVE-2024-45492 fixed in 2.6.3-r0
- Medium CVE-2023-52426 fixed in 2.6.0-r0
- Medium CVE-2024-50602 fixed in 2.6.4-r0
High 7 known vulnerabilities in tar@6.1.11 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update tar from 6.1.11 to 7.5.8 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.5.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-26960 fixed in 7.5.8
- High CVE-2026-23745 fixed in 7.5.3
- High CVE-2026-24842 fixed in 7.5.7
- High CVE-2026-29786 fixed in 7.5.10
- High CVE-2026-31802 fixed in 7.5.11
- High CVE-2026-23950 fixed in 7.5.4
- Medium CVE-2024-28863 fixed in 6.2.1
High 7 known vulnerabilities in expat@2.5.0-r0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update expat from 2.5.0-r0 to 2.6.0-r0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.6.0-r0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-52425 fixed in 2.6.0-r0
- High CVE-2024-28757 fixed in 2.6.2-r0
- High CVE-2024-45490 fixed in 2.6.3-r0
- High CVE-2024-45491 fixed in 2.6.3-r0
- High CVE-2024-45492 fixed in 2.6.3-r0
- Medium CVE-2023-52426 fixed in 2.6.0-r0
- Medium CVE-2024-50602 fixed in 2.6.4-r0
High 7 known vulnerabilities in tar@6.1.11 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update tar from 6.1.11 to 7.5.8 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.5.8); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-26960 fixed in 7.5.8
- High CVE-2026-23745 fixed in 7.5.3
- High CVE-2026-24842 fixed in 7.5.7
- High CVE-2026-29786 fixed in 7.5.10
- High CVE-2026-31802 fixed in 7.5.11
- High CVE-2026-23950 fixed in 7.5.4
- Medium CVE-2024-28863 fixed in 6.2.1
High 5 known vulnerabilities in sanitize-html@1.27.5 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update sanitize-html from 1.27.5 to 2.7.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.7.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-25887 fixed in 2.7.1
- Medium CVE-2021-26539 fixed in 2.3.1
- Medium CVE-2021-26540 fixed in 2.3.2
- Medium CVE-2024-21501 fixed in 2.12.1
- Medium CVE-2019-25225 fixed in 2.0.0-beta
High 5 known vulnerabilities in sanitize-html@1.27.5 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update sanitize-html from 1.27.5 to 2.7.1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.7.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-25887 fixed in 2.7.1
- Medium CVE-2021-26539 fixed in 2.3.1
- Medium CVE-2021-26540 fixed in 2.3.2
- Medium CVE-2024-21501 fixed in 2.12.1
- Medium CVE-2019-25225 fixed in 2.0.0-beta
High 4 known vulnerabilities in path-to-regexp@0.1.7 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update path-to-regexp from 0.1.7 to 0.1.13 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.1.13); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-4867 fixed in 0.1.13
- High CVE-2024-45296 fixed in 1.9.0
- High CVE-2024-45296 fixed in 0.1.10
- High CVE-2024-52798 fixed in 0.1.12
High 4 known vulnerabilities in path-to-regexp@0.1.7 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update path-to-regexp from 0.1.7 to 0.1.13 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.1.13); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-4867 fixed in 0.1.13
- High CVE-2024-45296 fixed in 0.1.10
- High CVE-2024-45296 fixed in 1.9.0
- High CVE-2024-52798 fixed in 0.1.12
High 4 known vulnerabilities in v4@4.8.1 (openg2p/simple-mpesa:v0.1-alpha)
How to fix
Update v4 from 4.8.1 to 4.18.2 or later in openg2p/simple-mpesa:v0.1-alpha. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.18.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2024-27304 fixed in 4.18.2
- High CVE-2024-27289 fixed in 4.18.2
- High GHSA-7jwh-3vrq-q3m8 fixed in 4.18.2
- Low CVE-2026-41889 fixed in no fix yet
High 3 known vulnerabilities in jsonwebtoken@8.5.1 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update jsonwebtoken from 8.5.1 to 9.0.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-23539 fixed in 9.0.0
- Medium CVE-2022-23541 fixed in 9.0.0
- Medium CVE-2022-23540 fixed in 9.0.0
High 3 known vulnerabilities in lodash@4.17.21 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update lodash from 4.17.21 to 4.18.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-4800 fixed in 4.18.0
- Medium CVE-2026-2950 fixed in 4.18.0
- Medium CVE-2025-13465 fixed in 4.17.23
High 3 known vulnerabilities in nghttp2@1.51.0-r0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update nghttp2 from 1.51.0-r0 to 1.51.0-r1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.51.0-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-35945 fixed in 1.51.0-r1
- High CVE-2023-44487 fixed in 1.51.0-r2
- Medium CVE-2024-28182 fixed in no fix yet
High 3 known vulnerabilities in semver@6.3.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update semver from 6.3.0 to 6.3.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.3.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-25883 fixed in 6.3.1
- High CVE-2022-25883 fixed in 7.5.2
- High CVE-2022-25883 fixed in 5.7.2
High 3 known vulnerabilities in jsonwebtoken@8.5.1 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update jsonwebtoken from 8.5.1 to 9.0.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 9.0.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-23539 fixed in 9.0.0
- Medium CVE-2022-23541 fixed in 9.0.0
- Medium CVE-2022-23540 fixed in 9.0.0
High 3 known vulnerabilities in lodash@4.17.21 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update lodash from 4.17.21 to 4.18.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-4800 fixed in 4.18.0
- Medium CVE-2026-2950 fixed in 4.18.0
- Medium CVE-2025-13465 fixed in 4.17.23
High 3 known vulnerabilities in nghttp2@1.51.0-r0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update nghttp2 from 1.51.0-r0 to 1.51.0-r1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.51.0-r1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2023-35945 fixed in 1.51.0-r1
- High CVE-2023-44487 fixed in 1.51.0-r2
- Medium CVE-2024-28182 fixed in no fix yet
High 3 known vulnerabilities in semver@6.3.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update semver from 6.3.0 to 6.3.1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.3.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-25883 fixed in 6.3.1
- High CVE-2022-25883 fixed in 5.7.2
- High CVE-2022-25883 fixed in 7.5.2
High 2 known vulnerabilities in content@5.0.2 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update content from 5.0.2 to 6.0.2 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.0.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2026-44974 fixed in 6.0.2
- High CVE-2026-35213 fixed in 6.0.1
High 2 known vulnerabilities in ejs@2.7.4 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update ejs from 2.7.4 to 3.1.7 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.1.7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2022-29078 fixed in 3.1.7
- Medium CVE-2024-33883 fixed in 3.1.10
High 2 known vulnerabilities in form-data@2.3.3 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update form-data from 2.3.3 to 2.5.4 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 2.5.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- High CVE-2025-7783 fixed in 2.5.4
- High CVE-2025-7783 fixed in 3.0.4
and 33 more groups with 47 findings
Medium 82
Medium 4 known vulnerabilities in ajv@6.12.6 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update ajv from 6.12.6 to 8.18.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-69873 fixed in 8.18.0
- Medium CVE-2025-69873 fixed in 8.18.0
- Medium CVE-2025-69873 fixed in 8.18.0
- Medium CVE-2020-15366 fixed in 6.12.3
Medium 4 known vulnerabilities in brace-expansion@2.0.1 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update brace-expansion from 2.0.1 to 5.0.5 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.0.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-33750 fixed in 5.0.5
- Medium CVE-2026-33750 fixed in 5.0.5
- Low CVE-2025-5889 fixed in 2.0.2
- Low CVE-2025-5889 fixed in 1.1.12
Medium 4 known vulnerabilities in busybox@1.35.0-r29 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update busybox from 1.35.0-r29 to 1.35.0-r31 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.35.0-r31); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-42363 fixed in 1.35.0-r31
- Medium CVE-2023-42364 fixed in 1.35.0-r31
- Medium CVE-2023-42365 fixed in 1.35.0-r31
- Medium CVE-2023-42366 fixed in 1.35.0-r30
Medium 4 known vulnerabilities in ajv@5.5.2 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update ajv from 5.5.2 to 8.18.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.18.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-69873 fixed in 8.18.0
- Medium CVE-2025-69873 fixed in 8.18.0
- Medium CVE-2025-69873 fixed in 8.18.0
- Medium CVE-2020-15366 fixed in 6.12.3
Medium 4 known vulnerabilities in brace-expansion@1.1.11 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update brace-expansion from 1.1.11 to 5.0.5 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.0.5); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-33750 fixed in 5.0.5
- Medium CVE-2026-33750 fixed in 5.0.5
- Low CVE-2025-5889 fixed in 2.0.2
- Low CVE-2025-5889 fixed in 1.1.12
Medium 4 known vulnerabilities in busybox@1.35.0-r29 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update busybox from 1.35.0-r29 to 1.35.0-r31 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.35.0-r31); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-42363 fixed in 1.35.0-r31
- Medium CVE-2023-42364 fixed in 1.35.0-r31
- Medium CVE-2023-42365 fixed in 1.35.0-r31
- Medium CVE-2023-42366 fixed in 1.35.0-r30
Medium 4 known vulnerabilities in busybox@1.36.1-r2 (openg2p/simple-mpesa:v0.1-alpha)
How to fix
Update busybox from 1.36.1-r2 to 1.36.1-r7 or later in openg2p/simple-mpesa:v0.1-alpha. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.36.1-r7); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-42363 fixed in 1.36.1-r7
- Medium CVE-2023-42364 fixed in 1.36.1-r7
- Medium CVE-2023-42365 fixed in 1.36.1-r7
- Medium CVE-2023-42366 fixed in 1.36.1-r6
Medium 3 known vulnerabilities in follow-redirects@1.15.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update follow-redirects from 1.15.0 to 1.15.4 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.15.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-26159 fixed in 1.15.4
- Medium CVE-2024-28849 fixed in 1.15.6
- Medium GHSA-r4q5-vmmm-2653 fixed in 1.16.0
Medium 3 known vulnerabilities in qs@6.5.3 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update qs from 6.5.3 to 6.14.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.14.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-15284 fixed in 6.14.1
- Medium CVE-2025-15284 fixed in 6.14.1
- Low CVE-2026-2391 fixed in 6.14.2
Medium 3 known vulnerabilities in follow-redirects@1.15.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update follow-redirects from 1.15.0 to 1.15.4 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.15.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-26159 fixed in 1.15.4
- Medium CVE-2024-28849 fixed in 1.15.6
- Medium GHSA-r4q5-vmmm-2653 fixed in 1.16.0
Medium 3 known vulnerabilities in qs@6.5.3 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update qs from 6.5.3 to 6.14.1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 6.14.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-15284 fixed in 6.14.1
- Medium CVE-2025-15284 fixed in 6.14.1
- Low CVE-2026-2391 fixed in 6.14.2
Medium 2 known vulnerabilities in express@4.18.1 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update express from 4.18.1 to 4.19.2 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.19.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-29041 fixed in 4.19.2
- Low CVE-2024-43796 fixed in 4.20.0
Medium 2 known vulnerabilities in postcss@7.0.39 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update postcss from 7.0.39 to 8.4.31 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.4.31); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-44270 fixed in 8.4.31
- Medium CVE-2026-41305 fixed in 8.5.10
Medium 2 known vulnerabilities in sqlite@3.40.1-r0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
No fixed version of sqlite is available yet. Check whether lalithkota/sp-con-payment-manager-core-connector:develop needs sqlite at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2024-0232 fixed in no fix yet
- Medium CVE-2023-7104 fixed in 3.40.1-r1
Medium 2 known vulnerabilities in express@4.18.1 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update express from 4.18.1 to 4.19.2 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.19.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2024-29041 fixed in 4.19.2
- Low CVE-2024-43796 fixed in 4.20.0
Medium 2 known vulnerabilities in postcss@7.0.39 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update postcss from 7.0.39 to 8.4.31 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 8.4.31); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-44270 fixed in 8.4.31
- Medium CVE-2026-41305 fixed in 8.5.10
Medium 2 known vulnerabilities in sqlite@3.40.1-r0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
No fixed version of sqlite is available yet. Check whether lalithkota/sp-con-payments-interop-layer:develop needs sqlite at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2024-0232 fixed in no fix yet
- Medium CVE-2023-7104 fixed in 3.40.1-r1
Medium 2 known vulnerabilities in sys@0.0.0-20200909081042-eff7692f9009 (openg2p/simple-mpesa:v0.1-alpha)
How to fix
Update sys from 0.0.0-20200909081042-eff7692f9009 to 0.0.0-20220412211240-33da011f77ad or later in openg2p/simple-mpesa:v0.1-alpha. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.0.0-20220412211240-33da011f77ad); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-29526 fixed in 0.0.0-20220412211240-33da011f77ad
- Low CVE-2026-39824 fixed in 0.44.0
Medium 1 known vulnerability in gcc@12.2.1_git20220924-r4 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
No fixed version of gcc is available yet. Check whether lalithkota/sp-con-payment-manager-core-connector:develop needs gcc at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-4039 fixed in no fix yet
Medium 1 known vulnerability in js-yaml@4.1.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update js-yaml from 4.1.0 to 4.1.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-64718 fixed in 4.1.1
Medium 1 known vulnerability in jsonpointer@4.1.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update jsonpointer from 4.1.0 to 5.0.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.0.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2021-23807 fixed in 5.0.0
Medium 1 known vulnerability in markdown-it@10.0.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update markdown-it from 10.0.0 to 12.3.2 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 12.3.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-21670 fixed in 12.3.2
Medium 1 known vulnerability in request@2.88.2 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
No fixed version of request is available yet. Check whether lalithkota/sp-con-payment-manager-core-connector:develop needs request at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-28155 fixed in no fix yet
Medium 1 known vulnerability in runtime@7.17.9 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update runtime from 7.17.9 to 7.26.10 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.26.10); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-27789 fixed in 7.26.10
Medium 1 known vulnerability in tough-cookie@2.5.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update tough-cookie from 2.5.0 to 4.1.3 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-26136 fixed in 4.1.3
Medium 1 known vulnerability in utf8@1.1.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update utf8 from 1.1.0 to 1.1.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-44288 fixed in 1.1.1
Medium 1 known vulnerability in uuid@3.4.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update uuid from 3.4.0 to 11.1.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 11.1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-41907 fixed in 11.1.1
Medium 1 known vulnerability in word-wrap@1.2.3 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update word-wrap from 1.2.3 to 1.2.4 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.2.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-26115 fixed in 1.2.4
Medium 1 known vulnerability in wreck@17.2.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update wreck from 17.2.0 to 18.1.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 18.1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-44979 fixed in 18.1.1
Medium 1 known vulnerability in xz@5.2.9-r0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
No fixed version of xz is available yet. Check whether lalithkota/sp-con-payment-manager-core-connector:develop needs xz at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2024-47611 fixed in no fix yet
Medium 1 known vulnerability in yaml@1.10.2 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update yaml from 1.10.2 to 1.10.3 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.10.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-33532 fixed in 1.10.3
Medium 1 known vulnerability in yargs-parser@11.1.1 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update yargs-parser from 11.1.1 to 13.1.2 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 13.1.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2020-7608 fixed in 13.1.2
Medium 1 known vulnerability in gcc@12.2.1_git20220924-r4 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
No fixed version of gcc is available yet. Check whether lalithkota/sp-con-payments-interop-layer:develop needs gcc at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-4039 fixed in no fix yet
Medium 1 known vulnerability in js-yaml@4.1.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update js-yaml from 4.1.0 to 4.1.1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-64718 fixed in 4.1.1
Medium 1 known vulnerability in jsonpointer@4.1.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update jsonpointer from 4.1.0 to 5.0.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.0.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2021-23807 fixed in 5.0.0
Medium 1 known vulnerability in markdown-it@10.0.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update markdown-it from 10.0.0 to 12.3.2 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 12.3.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2022-21670 fixed in 12.3.2
Medium 1 known vulnerability in request@2.88.2 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
No fixed version of request is available yet. Check whether lalithkota/sp-con-payments-interop-layer:develop needs request at all (a slimmer or distroless base image often drops it), watch the advisory for a fix, or accept the risk with a review date if it isn't reachable in your setup.
Vulnerabilities
- Medium CVE-2023-28155 fixed in no fix yet
Medium 1 known vulnerability in runtime@7.17.9 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update runtime from 7.17.9 to 7.26.10 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 7.26.10); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2025-27789 fixed in 7.26.10
Medium 1 known vulnerability in tough-cookie@2.5.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update tough-cookie from 2.5.0 to 4.1.3 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.1.3); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2023-26136 fixed in 4.1.3
Medium 1 known vulnerability in utf8@1.1.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update utf8 from 1.1.0 to 1.1.1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Medium CVE-2026-44288 fixed in 1.1.1
and 6 more groups with 6 findings
Low 16
Low 2 known vulnerabilities in cookie@0.5.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update cookie from 0.5.0 to 0.7.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.7.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2024-47764 fixed in 0.7.0
- Low CVE-2024-47764 fixed in 0.7.0
Low 2 known vulnerabilities in diff@4.0.2 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update diff from 4.0.2 to 4.0.4 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 4.0.4); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2026-24001 fixed in 4.0.4
- Low CVE-2026-24001 fixed in 5.2.2
Low 2 known vulnerabilities in cookie@0.5.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update cookie from 0.5.0 to 0.7.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.7.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2024-47764 fixed in 0.7.0
- Low CVE-2024-47764 fixed in 0.7.0
Low 2 known vulnerabilities in diff@5.1.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update diff from 5.1.0 to 5.2.2 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 5.2.2); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2026-24001 fixed in 5.2.2
- Low CVE-2026-24001 fixed in 4.0.4
Low 1 known vulnerability in on-headers@1.0.2 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update on-headers from 1.0.2 to 1.1.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2025-7339 fixed in 1.1.0
Low 1 known vulnerability in once@2.0.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update once from 2.0.0 to 3.0.1 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2026-3449 fixed in 3.0.1
Low 1 known vulnerability in send@0.18.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update send from 0.18.0 to 0.19.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.19.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2024-43799 fixed in 0.19.0
Low 1 known vulnerability in serve-static@1.15.0 (lalithkota/sp-con-payment-manager-core-connector:develop)
How to fix
Update serve-static from 1.15.0 to 1.16.0 or later in lalithkota/sp-con-payment-manager-core-connector:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.16.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2024-43800 fixed in 1.16.0
Low 1 known vulnerability in on-headers@1.0.2 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update on-headers from 1.0.2 to 1.1.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.1.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2025-7339 fixed in 1.1.0
Low 1 known vulnerability in once@2.0.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update once from 2.0.0 to 3.0.1 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 3.0.1); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2026-3449 fixed in 3.0.1
Low 1 known vulnerability in send@0.18.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update send from 0.18.0 to 0.19.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 0.19.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2024-43799 fixed in 0.19.0
Low 1 known vulnerability in serve-static@1.15.0 (lalithkota/sp-con-payments-interop-layer:develop)
How to fix
Update serve-static from 1.15.0 to 1.16.0 or later in lalithkota/sp-con-payments-interop-layer:develop. If the package comes from the base image, move to a newer base image tag (or rebuild on the current one, then check that it ships 1.16.0); if your application installs it, bump it in its dependency file. Rebuild, push, update the image tag where it's deployed, and scan again.
Vulnerabilities
- Low CVE-2024-43800 fixed in 1.16.0
Grades use InfraScan Cloud's current formula, so they can differ from the ones first shown for this scan. Findings reflect the repository on 1 Jun 2026; it may have changed since.
Scan your own repository
InfraScan Cloud scans your repositories and AWS accounts, keeps the history and shows how to fix each finding.