ai-security-scanner / security report

Redacted assessment case

Selected run
cace89a3-0d9b-474b-b3dd-bff17d6c0f9a
Last saved
2026-10-07 01:38:04 UTC
Run state
Complete
8Problems found
8Checks completed
0Partly completed
0Failed
0Timed out
0Not tested
0Coverage gaps
0Record notes

In short

This run included 1 asset. It completed 8 checks for 1 asset.

8 problems were found, 1 of them Critical or High severity.

Start with “A subprocess launched through a shell can allow command injection”: Change the code to remove the reported unsafe pattern.

Compared with the earlier scan

Compared with Scan 1, finished 2026-10-07 01:24:36 UTC.

6No longer observed
7Still present
1New
0Verification incomplete

1 of the still-present problems only moved to another line in the same file.

No longer observed

The same completed check no longer found this problem. Review the new evidence, then close it.

A secret removed from the files can still be read from version history and copies made earlier. Revoke or rotate it.

New

Original findings compared
Scan run IDs
Before-fix scan
0a8a64dd-2993-40d0-92c3-aa994a032acd
After-fix check
cace89a3-0d9b-474b-b3dd-bff17d6c0f9a

Folder copies compared

Problems by severity

Severity describes possible impact. It is the scanner's rating where one was given, and this product's stated basis where none was.

Critical0
High1
Medium4
Low2
Informational0
Unknown1

What each check reached

One row per requested asset, one column per check in this run. An empty cell means no check of that kind was planned for that asset, which is not a result.

AssetCheckovGitleaksGrypeKICSSemgrepSyftTrivyTruffleHog
Asset 1

Which assets need attention

Every selected asset appears once. A no-problem result applies only to the security checks that completed.

AssetWhat this run showsSeverity mix
Asset 1RepositoryProblems found

High 1 · Medium 4 · Low 2 · Unknown 1

Next step: Problems found — review this asset's highest-priority problem first.

What you asked to scan

Targets

Requested checks

Limits

What was actually tested

Scan period: 2026-10-07 01:26:25 UTC to 2026-10-07 01:38:04 UTC

CheckStateTargetsStartedFinished
Trivy
Version 0.74.0 · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:35:28 UTC
Checkov
Version 3.3.13 · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:36:49 UTC
KICS
Version 2.1.20 · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:35:58 UTC
Grype
Version 0.117.0 · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:37:53 UTC
Syft
Version 1.51.0 · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:38:04 UTC
Gitleaks
Version 8.30.1 · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:26:59 UTC
Semgrep
Version 1.174.0 (source a0c13f3) · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:34:58 UTC
TruffleHog
Version 3.97.0 (source 3ab759f) · last updated 2026-08-24		CompletedAsset 12026-10-07 01:26:25 UTC2026-10-07 01:35:43 UTC

What was not tested

What to do next

Before changing anything: Capture the current configuration and test its restoration path before making the change.

  1. Change the code to remove the reported unsafe pattern. — 2 related problems call for this kind of change; each needs its own fix. The first is Detected user input entering a `subprocess` call unsafely. This could result in a command injection vulnerability. An attacker could use this vulnerability to execute arbitrary commands on the host, which allows them to download malware, scan sensitive data, or run any command they wish on the server. Do not let users choose the command to run. In general, prefer to use Python API versions of system commands. If you must use subprocess, use a dictionary to allowlist a set of commands. — High severity, High confidence — engine rating: HIGH
    To confirm: Rerun the same scan after the changes and confirm these problems are no longer reported. Suggested expert: Application security engineer
  2. Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix. — 4 related problems call for this kind of change; each needs its own fix. The first is Vulnerable package requests (GHSA-9wx4-h78v-vm56) — Medium severity, Medium confidence — this product's rating from an installed-version match against a published advisory range
    To confirm: Rerun the same scan after the changes and confirm these problems are no longer reported. Suggested expert: Software supply-chain engineer
  3. Correct the infrastructure-as-code template so redeployment does not restore the insecure setting. — 2 related problems call for this kind of change; each needs its own fix. The first is Healthcheck Instruction Missing — Low severity, High confidence — this product's rating from a deterministic policy or configuration evaluation
    To confirm: Rerun the same scan after the changes and confirm these problems are no longer reported. Suggested expert: Infrastructure-as-code engineer

Problems found

Problems follow the report order. Severity is the scanner's rating of possible impact (this product rates it only when the scanner did not), confidence describes evidence strength, and priority is this product's recommended order. When this product places a problem lower than its severity suggests, the card says why.

8 problems · 16 original findings

Confidence: where a scanner reported no confidence of its own, this product's rating comes from an installed-version match against a published advisory range; a deterministic policy or configuration evaluation.

#SeverityProblemAssetWhat to do next
1HighA subprocess launched through a shell can allow command injection.Asset 1Change the code to remove the reported unsafe pattern.
2MediumDetected Flask app with debug=True. Do not deploy to production with this flag enabled as it will leak sensitive information. Instead, consider using Flask configuration variables or setting 'debug' using system environment variables.Asset 1Change the code to remove the reported unsafe pattern.
3MediumVulnerable package requests 2.31.0 (CVE-2024-35195 / GHSA-9wx4-h78v-vm56)Asset 1Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.
4MediumVulnerable package requests 2.31.0 (CVE-2024-47081 / GHSA-9hjg-9r4m-mvj7)Asset 1Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.
5MediumVulnerable package requests 2.31.0 (CVE-2026-25645 / GHSA-gc5v-m9x4-r6x2)Asset 1Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.
6LowHealthcheck Instruction MissingAsset 1Correct the infrastructure-as-code template so redeployment does not restore the insecure setting.
7LowVulnerable package flask 3.0.3 (CVE-2026-27205 / GHSA-68rp-wp8r-4726)Asset 1Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.
8UnknownEnsure that HEALTHCHECK instructions have been added to container imagesAsset 1Correct the infrastructure-as-code template so redeployment does not restore the insecure setting.

A subprocess launched through a shell can allow command injection. — Asset 1

High · 5 original findings

Source code or credentials may permit unauthorized access or unsafe application behavior.

Target: Asset 1

What to do next: Change the code to remove the reported unsafe pattern.

Related checks (5)

Detected user input entering a `subprocess` call unsafely. This could result in a command injection vulnerability. An attacker could use this vulnerability to execute arbitrary commands on the host, which allows them to download malware, scan sensitive data, or run any command they wish on the server. Do not let users choose the command to run. In general, prefer to use Python API versions of system commands. If you must use subprocess, use a dictionary to allowlist a set of commands. — Asset 1

Severity: HighConfidence: Highengine rating: HIGHPriority: 80Report order #1Suggested expert: Application security engineer

Semgrep reported a high-severity condition on the assessed asset. Possible impact: Source code or credentials may permit unauthorized access or unsafe application behavior.

What to do next: Change the code to remove the reported unsafe pattern.

How to confirm the fix: Rerun Semgrep with the same scope after the change and confirm that source rule python.flask.security.injection.subprocess-injection.subprocess-injection is no longer reported.

Official scanner references: https://github.com/semgrep/semgrep · https://semgrep.dev/ · https://semgrep.dev/docs/cheat-sheets/python-command-injection/

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-345393569beccd54f6bea5e46bc227f6

Why this priority

  • Source severity: ERROR
  • Source confidence: HIGH

Evidence SHA-256

  • 1d2ad2c5a3c9af2fed7095b7c870681073a85ffc7a1bec4efe8876fc517bd2bc
    Evidence evidence-24cdce67b4524a9cd895dc86d3288f19 · Check semgrep · Observed 2026-10-07 01:34:58 UTC
    Source rule
    python.flask.security.injection.subprocess-injection.subprocess-injection
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Source Code
    Engine run ID
    ddfbdd4f-3c68-4f42-9af7-2eb64f6fecd4
    Artifact ID
    66921f2e-b840-4849-8f66-69e62ab8919a
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-assigned CWE
    CWE-78

Related framework references

  • OWASP Top 10 2021 / A03:2021 — Injection
    Relationship: related
    Why related: OWASP publishes A03:2021 as this set of CWEs, so a scanner-assigned CWE in the set places the result in the category.

A subprocess launched through a shell can allow command injection. — Asset 1

Severity: HighConfidence: Highengine rating: HIGHPriority: 80Report order #2Suggested expert: Application security engineer

Semgrep reported a high-severity condition on the assessed asset. Possible impact: Source code or credentials may permit unauthorized access or unsafe application behavior.

What to do next: Change the code to remove the reported unsafe pattern.

How to confirm the fix: Rerun Semgrep with the same scope after the change and confirm that source rule ai-security-scanner.python.shell-true is no longer reported.

Official scanner references: https://github.com/semgrep/semgrep · https://semgrep.dev/

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-e30c4507ca0672d1930ead1a1de9bc38

Why this priority

  • Source severity: ERROR
  • Source confidence: HIGH

Evidence SHA-256

  • 1d2ad2c5a3c9af2fed7095b7c870681073a85ffc7a1bec4efe8876fc517bd2bc
    Evidence evidence-4b38a87af90a024109c7a7e05fd8f539 · Check semgrep · Observed 2026-10-07 01:34:58 UTC
    Source rule
    ai-security-scanner.python.shell-true
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Source Code
    Engine run ID
    ddfbdd4f-3c68-4f42-9af7-2eb64f6fecd4
    Artifact ID
    66921f2e-b840-4849-8f66-69e62ab8919a
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-assigned CWE
    CWE-78

Related framework references

  • ISO/IEC 27001 2022 / A.8.28 — Secure coding practices
    Relationship: related
    Why related: Static-analysis evidence that Python code invokes an operating-system shell is related to secure development and pre-execution dangerous-construct checks. AIDEFEND's AI-generated-artifact coordinate applies when the selected code was generated or materially changed by AI.
  • ISO/IEC 27001 2022 / A.8.29 — Security testing before acceptance
    Relationship: related
    Why related: Static-analysis evidence that Python code invokes an operating-system shell is related to secure development and pre-execution dangerous-construct checks. AIDEFEND's AI-generated-artifact coordinate applies when the selected code was generated or materially changed by AI.
  • NIST CSF 2.0 / PR.PS-06 — Secure software development practices
    Relationship: related
    Why related: Static-analysis evidence that Python code invokes an operating-system shell is related to secure development and pre-execution dangerous-construct checks. AIDEFEND's AI-generated-artifact coordinate applies when the selected code was generated or materially changed by AI.
  • OWASP Top 10 2021 / A03:2021 — Injection
    Relationship: related
    Why related: OWASP publishes A03:2021 as this set of CWEs, so a scanner-assigned CWE in the set places the result in the category.

Detected subprocess function 'run' with user controlled data. A malicious actor could leverage this to perform command injection. You may consider using 'shlex.escape()'. — Asset 1

Severity: HighConfidence: Mediumengine rating: MEDIUMPriority: 80Report order #3Suggested expert: Application security engineer

Semgrep reported a high-severity condition on the assessed asset. Possible impact: Source code or credentials may permit unauthorized access or unsafe application behavior.

What to do next: Change the code to remove the reported unsafe pattern.

How to confirm the fix: Rerun Semgrep with the same scope after the change and confirm that source rule python.lang.security.dangerous-subprocess-use.dangerous-subprocess-use is no longer reported.

Official scanner references: https://docs.python.org/3/library/shlex.html · https://docs.python.org/3/library/subprocess.html · https://github.com/semgrep/semgrep · https://semgrep.dev/ · https://semgrep.dev/docs/cheat-sheets/python-command-injection/ · https://stackoverflow.com/questions/3172470/actual-meaning-of-shell-true-in-subprocess

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-2ead0ffc8cedc2e7de0c930af559f9d9

Why this priority

  • Source severity: ERROR
  • Source confidence: MEDIUM

Evidence SHA-256

  • 1d2ad2c5a3c9af2fed7095b7c870681073a85ffc7a1bec4efe8876fc517bd2bc
    Evidence evidence-9a3324107b79f11dd3ba264736b436f2 · Check semgrep · Observed 2026-10-07 01:34:58 UTC
    Source rule
    python.lang.security.dangerous-subprocess-use.dangerous-subprocess-use
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Source Code
    Engine run ID
    ddfbdd4f-3c68-4f42-9af7-2eb64f6fecd4
    Artifact ID
    66921f2e-b840-4849-8f66-69e62ab8919a
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-assigned CWE
    CWE-78

Related framework references

  • OWASP Top 10 2021 / A03:2021 — Injection
    Relationship: related
    Why related: OWASP publishes A03:2021 as this set of CWEs, so a scanner-assigned CWE in the set places the result in the category.

Found 'subprocess' function 'run' with 'shell=True'. This is dangerous because this call will spawn the command using a shell process. Doing so propagates current shell settings and variables, which makes it much easier for a malicious actor to execute commands. Use 'shell=False' instead. — Asset 1

Severity: HighConfidence: Mediumengine rating: MEDIUMPriority: 80Report order #4Suggested expert: Application security engineer

Semgrep reported a high-severity condition on the assessed asset. Possible impact: Source code or credentials may permit unauthorized access or unsafe application behavior.

What to do next: Change the code to remove the reported unsafe pattern.

Scanner-provided remediation: [redacted scanner-provided remediation]

How to confirm the fix: Rerun Semgrep with the same scope after the change and confirm that source rule python.lang.security.audit.subprocess-shell-true.subprocess-shell-true is no longer reported.

Official scanner references: https://docs.python.org/3/library/subprocess.html · https://github.com/semgrep/semgrep · https://semgrep.dev/ · https://stackoverflow.com/questions/3172470/actual-meaning-of-shell-true-in-subprocess

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-a416946d7e152b3c0cf170b0b01c1b0c

Why this priority

  • Source severity: ERROR
  • Source confidence: MEDIUM

Evidence SHA-256

  • 1d2ad2c5a3c9af2fed7095b7c870681073a85ffc7a1bec4efe8876fc517bd2bc
    Evidence evidence-5e1d497424eb308a420a759334568b06 · Check semgrep · Observed 2026-10-07 01:34:58 UTC
    Source rule
    python.lang.security.audit.subprocess-shell-true.subprocess-shell-true
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Source Code
    Engine run ID
    ddfbdd4f-3c68-4f42-9af7-2eb64f6fecd4
    Artifact ID
    66921f2e-b840-4849-8f66-69e62ab8919a
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided remediation
    [redacted scanner-provided remediation]
    Scanner-assigned CWE
    CWE-78

Related framework references

  • OWASP Top 10 2021 / A03:2021 — Injection
    Relationship: related
    Why related: OWASP publishes A03:2021 as this set of CWEs, so a scanner-assigned CWE in the set places the result in the category.

Detected subprocess function 'run' without a static string. If this data can be controlled by a malicious actor, it may be an instance of command injection. Audit the use of this call to ensure it is not controllable by an external resource. You may consider using 'shlex.escape()'. — Asset 1

Severity: HighConfidence: Lowengine rating: LOWPriority: 80Report order #5Suggested expert: Application security engineer

Semgrep reported a high-severity condition on the assessed asset. Possible impact: Source code or credentials may permit unauthorized access or unsafe application behavior.

What to do next: Change the code to remove the reported unsafe pattern.

How to confirm the fix: Rerun Semgrep with the same scope after the change and confirm that source rule python.lang.security.audit.dangerous-subprocess-use-audit.dangerous-subprocess-use-audit is no longer reported.

Official scanner references: https://docs.python.org/3/library/shlex.html · https://docs.python.org/3/library/subprocess.html · https://github.com/semgrep/semgrep · https://semgrep.dev/ · https://semgrep.dev/docs/cheat-sheets/python-command-injection/ · https://stackoverflow.com/questions/3172470/actual-meaning-of-shell-true-in-subprocess

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-057f327431190b7c09d49efeb94c2459

Why this priority

  • Source severity: ERROR
  • Source confidence: LOW

Evidence SHA-256

  • 1d2ad2c5a3c9af2fed7095b7c870681073a85ffc7a1bec4efe8876fc517bd2bc
    Evidence evidence-2509d415b86e780bb1b094d4cc2320a9 · Check semgrep · Observed 2026-10-07 01:34:58 UTC
    Source rule
    python.lang.security.audit.dangerous-subprocess-use-audit.dangerous-subprocess-use-audit
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Source Code
    Engine run ID
    ddfbdd4f-3c68-4f42-9af7-2eb64f6fecd4
    Artifact ID
    66921f2e-b840-4849-8f66-69e62ab8919a
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-assigned CWE
    CWE-78

Related framework references

  • OWASP Top 10 2021 / A03:2021 — Injection
    Relationship: related
    Why related: OWASP publishes A03:2021 as this set of CWEs, so a scanner-assigned CWE in the set places the result in the category.

Detected Flask app with debug=True. Do not deploy to production with this flag enabled as it will leak sensitive information. Instead, consider using Flask configuration variables or setting 'debug' using system environment variables. — Asset 1

Severity: MediumConfidence: Highengine rating: HIGHPriority: 60Report order #6Suggested expert: Application security engineer

Semgrep reported a medium-severity condition on the assessed asset. Possible impact: Source code or credentials may permit unauthorized access or unsafe application behavior.

What to do next: Change the code to remove the reported unsafe pattern.

How to confirm the fix: Rerun Semgrep with the same scope after the change and confirm that source rule python.flask.security.audit.debug-enabled.debug-enabled is no longer reported.

Official scanner references: https://github.com/semgrep/semgrep · https://labs.detectify.com/2015/10/02/how-patreon-got-hacked-publicly-exposed-werkzeug-debugger/ · https://semgrep.dev/

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-12218cf70e07c8fc7ccee015bb68b93b

Why this priority

Evidence SHA-256

Related framework references

Vulnerable package requests 2.31.0 (CVE-2024-35195 / GHSA-9wx4-h78v-vm56) — Asset 1

Medium · 2 original findings

A container or software component may expose the workload to a known weakness.

Target: Asset 1

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Related checks (2)

Vulnerable package requests (GHSA-9wx4-h78v-vm56) — Asset 1

Severity: MediumConfidence: MediumPriority: 60Report order #7Suggested expert: Software supply-chain engineer

Grype reported a medium-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 2.32.0

How to confirm the fix: Rerun Grype with the same scope after the change and confirm that source rule GHSA-9wx4-h78v-vm56 is no longer reported.

Official scanner references: https://github.com/advisories/GHSA-9wx4-h78v-vm56 · https://github.com/anchore/grype · https://github.com/psf/requests/commit/a58d7f2ffb4d00b46dca2d70a3932a0b37e22fac · https://github.com/psf/requests/pull/6655 · https://github.com/psf/requests/security/advisories/GHSA-9wx4-h78v-vm56 · https://nvd.nist.gov/vuln/detail/CVE-2024-35195

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-5b53f827c1a255e6cc6b436c74593288

Why this priority

  • Source severity: Medium
  • Confidence derived from an installed-version match against a published advisory range; Grype reports no confidence of its own.

Evidence SHA-256

  • 8ea94f90312ba26c32607ea526ba7e3b06881ffe1fb22abb63fb8b9e30316680
    Evidence evidence-3fefc6768423c9a7926cb96a7fdf07ef · Check grype · Observed 2026-10-07 01:37:52 UTC
    Source rule
    GHSA-9wx4-h78v-vm56
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    61b950c1-ddf7-4e28-b77c-8f59ce9b926a
    Artifact ID
    0699b40c-764b-4284-970f-57b74f63d374
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    2.31.0
    Scanner-provided fixed version
    2.32.0
    Scanner-reported CVSS
    5.6 · v3.1 · scored by grype
    CVSS vector
    CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N

Related framework references

  • The packaged mapping catalog has no entry for this finding's rule, so its framework position is unknown, not absent.

requests: subsequent requests to the same host ignore cert verification — Asset 1

Severity: MediumConfidence: MediumPriority: 60Report order #10Suggested expert: Software supply-chain engineer

Trivy reported a medium-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 2.32.0

How to confirm the fix: Rerun Trivy with the same scope after the change and confirm that source rule CVE-2024-35195 is no longer reported.

Official scanner references: https://access.redhat.com/errata/RHSA-2025:0012 · https://access.redhat.com/errata/RHSA-2025:7049 · https://access.redhat.com/security/cve/CVE-2024-35195 · https://avd.aquasec.com/nvd/cve-2024-35195 · https://bugzilla.redhat.com/2282114 · https://bugzilla.redhat.com/show_bug.cgi?id=2282114 · https://creativecommons.org/licenses/by/4.0/ · https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-35195 · https://errata.almalinux.org/8/ALSA-2025-0012.html · https://errata.rockylinux.org/RLSA-2025:7049 · https://github.com/aquasecurity/trivy · https://github.com/psf/requests

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-86fc7db742db356b157deae422f8338a

Why this priority

  • Source severity: MEDIUM
  • Confidence derived from an installed-version match against a published advisory range; Trivy reports no confidence of its own.

Evidence SHA-256

  • 95af5c40a8cd3504bc9fd07b9db2846db951574326518d58a803aaada8a948a2
    Evidence evidence-faba1c7747969f1e0be8258ceb330f21 · Check trivy · Observed 2026-10-07 01:35:28 UTC
    Source rule
    CVE-2024-35195
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    00707d6c-ca99-4ddd-9708-8a4e2aa0b30b
    Artifact ID
    afa6f00a-3bce-4b71-ac77-d936a6848cb9
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    2.31.0
    Scanner-provided fixed version
    2.32.0
    Scanner-assigned CWE
    CWE-670
    Scanner-reported CVSS
    5.6 · v3.1 · scored by ghsa
    CVSS vector
    CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N
    Scanner-reported CVSS
    5.6 · v3.1 · scored by redhat
    CVSS vector
    CVSS:3.1/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N

Related framework references

  • ISO/IEC 27001 2022 / A.8.8 — Technical vulnerability handling
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • NIST CSF 2.0 / ID.RA-01 — Vulnerability identification and recording
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • OWASP Top 10 2021 / A06:2021 — Vulnerable and Outdated Components
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.

Vulnerable package requests 2.31.0 (CVE-2024-47081 / GHSA-9hjg-9r4m-mvj7) — Asset 1

Medium · 2 original findings

A container or software component may expose the workload to a known weakness.

Target: Asset 1

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Related checks (2)

requests: Requests vulnerable to .netrc credentials leak via malicious URLs — Asset 1

Severity: MediumConfidence: MediumPriority: 60Report order #8Suggested expert: Software supply-chain engineer

Trivy reported a medium-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 2.32.4

How to confirm the fix: Rerun Trivy with the same scope after the change and confirm that source rule CVE-2024-47081 is no longer reported.

Official scanner references: https://access.redhat.com/errata/RHSA-2025:12519 · https://access.redhat.com/errata/RHSA-2025:14999 · https://access.redhat.com/security/cve/CVE-2024-47081 · https://avd.aquasec.com/nvd/cve-2024-47081 · https://bugzilla.redhat.com/2371272 · https://bugzilla.redhat.com/show_bug.cgi?id=2371272 · https://creativecommons.org/licenses/by/4.0/ · https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-47081 · https://errata.almalinux.org/8/ALSA-2025-14999.html · https://errata.rockylinux.org/RLSA-2025:12519 · https://github.com/aquasecurity/trivy · https://github.com/psf/requests

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-6bfac04ddf36753a1953d3df50d9dbe5

Why this priority

  • Source severity: MEDIUM
  • Confidence derived from an installed-version match against a published advisory range; Trivy reports no confidence of its own.

Evidence SHA-256

  • 95af5c40a8cd3504bc9fd07b9db2846db951574326518d58a803aaada8a948a2
    Evidence evidence-7d8f5d731bb3afd58636a613fca1ccc7 · Check trivy · Observed 2026-10-07 01:35:28 UTC
    Source rule
    CVE-2024-47081
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    00707d6c-ca99-4ddd-9708-8a4e2aa0b30b
    Artifact ID
    afa6f00a-3bce-4b71-ac77-d936a6848cb9
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    2.31.0
    Scanner-provided fixed version
    2.32.4
    Scanner-assigned CWE
    CWE-522
    Scanner-reported CVSS
    5.3 · v3.1 · scored by ghsa
    CVSS vector
    CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
    Scanner-reported CVSS
    5.3 · v3.1 · scored by redhat
    CVSS vector
    CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Related framework references

  • ISO/IEC 27001 2022 / A.8.8 — Technical vulnerability handling
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • NIST CSF 2.0 / ID.RA-01 — Vulnerability identification and recording
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • OWASP Top 10 2021 / A06:2021 — Vulnerable and Outdated Components
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • OWASP Top 10 2021 / A04:2021 — Insecure Design
    Relationship: related
    Why related: OWASP publishes A04:2021 as this set of CWEs, so a scanner-assigned CWE in the set places the result in the category.

Vulnerable package requests (GHSA-9hjg-9r4m-mvj7) — Asset 1

Severity: MediumConfidence: MediumPriority: 60Report order #11Suggested expert: Software supply-chain engineer

Grype reported a medium-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 2.32.4

How to confirm the fix: Rerun Grype with the same scope after the change and confirm that source rule GHSA-9hjg-9r4m-mvj7 is no longer reported.

Official scanner references: https://github.com/advisories/GHSA-9hjg-9r4m-mvj7 · https://github.com/anchore/grype · https://github.com/psf/requests/commit/96ba401c1296ab1dda74a2365ef36d88f7d144ef · https://github.com/psf/requests/pull/6965 · https://github.com/psf/requests/security/advisories/GHSA-9hjg-9r4m-mvj7 · https://nvd.nist.gov/vuln/detail/CVE-2024-47081 · https://requests.readthedocs.io/en/latest/api/#requests.Session.trust_env · https://seclists.org/fulldisclosure/2025/Jun/2

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-93221aeb57ed723e1b1fea0b87b981ff

Why this priority

  • Source severity: Medium
  • Confidence derived from an installed-version match against a published advisory range; Grype reports no confidence of its own.

Evidence SHA-256

  • 8ea94f90312ba26c32607ea526ba7e3b06881ffe1fb22abb63fb8b9e30316680
    Evidence evidence-3102b7eed16b7a2983eeb92927f8a92d · Check grype · Observed 2026-10-07 01:37:52 UTC
    Source rule
    GHSA-9hjg-9r4m-mvj7
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    61b950c1-ddf7-4e28-b77c-8f59ce9b926a
    Artifact ID
    0699b40c-764b-4284-970f-57b74f63d374
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    2.31.0
    Scanner-provided fixed version
    2.32.4
    Scanner-reported CVSS
    5.3 · v3.1 · scored by grype
    CVSS vector
    CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Related framework references

  • The packaged mapping catalog has no entry for this finding's rule, so its framework position is unknown, not absent.

Vulnerable package requests 2.31.0 (CVE-2026-25645 / GHSA-gc5v-m9x4-r6x2) — Asset 1

Medium · 2 original findings

A container or software component may expose the workload to a known weakness.

Target: Asset 1

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Related checks (2)

Vulnerable package requests (GHSA-gc5v-m9x4-r6x2) — Asset 1

Severity: MediumConfidence: MediumPriority: 60Report order #9Suggested expert: Software supply-chain engineer

Grype reported a medium-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 2.33.0

How to confirm the fix: Rerun Grype with the same scope after the change and confirm that source rule GHSA-gc5v-m9x4-r6x2 is no longer reported.

Official scanner references: https://github.com/advisories/GHSA-gc5v-m9x4-r6x2 · https://github.com/anchore/grype · https://github.com/psf/requests/commit/66d21cb07bd6255b1280291c4fafb71803cdb3b7 · https://github.com/psf/requests/releases/tag/v2.33.0 · https://github.com/psf/requests/security/advisories/GHSA-gc5v-m9x4-r6x2 · https://nvd.nist.gov/vuln/detail/CVE-2026-25645

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-821475b53601212ae24027e9fb0bd772

Why this priority

  • Source severity: Medium
  • Confidence derived from an installed-version match against a published advisory range; Grype reports no confidence of its own.

Evidence SHA-256

  • 8ea94f90312ba26c32607ea526ba7e3b06881ffe1fb22abb63fb8b9e30316680
    Evidence evidence-5c291704f7ab21ad2d70a40ef9b2be8e · Check grype · Observed 2026-10-07 01:37:52 UTC
    Source rule
    GHSA-gc5v-m9x4-r6x2
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    61b950c1-ddf7-4e28-b77c-8f59ce9b926a
    Artifact ID
    0699b40c-764b-4284-970f-57b74f63d374
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    2.31.0
    Scanner-provided fixed version
    2.33.0
    Scanner-reported CVSS
    4.4 · v3.1 · scored by grype
    CVSS vector
    CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N

Related framework references

  • The packaged mapping catalog has no entry for this finding's rule, so its framework position is unknown, not absent.

requests: Requests: Security bypass due to predictable temporary file creation — Asset 1

Severity: MediumConfidence: MediumPriority: 60Report order #12Suggested expert: Software supply-chain engineer

Trivy reported a medium-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 2.33.0

How to confirm the fix: Rerun Trivy with the same scope after the change and confirm that source rule CVE-2026-25645 is no longer reported.

Official scanner references: https://access.redhat.com/security/cve/CVE-2026-25645 · https://avd.aquasec.com/nvd/cve-2026-25645 · https://github.com/aquasecurity/trivy · https://github.com/psf/requests · https://github.com/psf/requests/commit/66d21cb07bd6255b1280291c4fafb71803cdb3b7 · https://github.com/psf/requests/releases/tag/v2.33.0 · https://github.com/psf/requests/security/advisories/GHSA-gc5v-m9x4-r6x2 · https://nvd.nist.gov/vuln/detail/CVE-2026-25645 · https://trivy.dev/ · https://www.cve.org/CVERecord?id=CVE-2026-25645

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-b6575e638285a44a0c8937e97f9287fe

Why this priority

  • Source severity: MEDIUM
  • Confidence derived from an installed-version match against a published advisory range; Trivy reports no confidence of its own.

Evidence SHA-256

  • 95af5c40a8cd3504bc9fd07b9db2846db951574326518d58a803aaada8a948a2
    Evidence evidence-e60edc00cd6a21c5630078af0dbfe733 · Check trivy · Observed 2026-10-07 01:35:28 UTC
    Source rule
    CVE-2026-25645
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    00707d6c-ca99-4ddd-9708-8a4e2aa0b30b
    Artifact ID
    afa6f00a-3bce-4b71-ac77-d936a6848cb9
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    2.31.0
    Scanner-provided fixed version
    2.33.0
    Scanner-assigned CWE
    CWE-377
    Scanner-reported CVSS
    4.4 · v3.1 · scored by ghsa
    CVSS vector
    CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N
    Scanner-reported CVSS
    5.5 · v3.1 · scored by nvd
    CVSS vector
    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
    Scanner-reported CVSS
    4.7 · v3.1 · scored by redhat
    CVSS vector
    CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N

Related framework references

  • ISO/IEC 27001 2022 / A.8.8 — Technical vulnerability handling
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • NIST CSF 2.0 / ID.RA-01 — Vulnerability identification and recording
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • OWASP Top 10 2021 / A06:2021 — Vulnerable and Outdated Components
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • OWASP Top 10 2021 / A01:2021 — Broken Access Control
    Relationship: related
    Why related: OWASP publishes A01:2021 as this set of CWEs, so a scanner-assigned CWE in the set places the result in the category.

Healthcheck Instruction Missing — Asset 1

Severity: LowConfidence: HighPriority: 35Report order #13Suggested expert: Infrastructure-as-code engineer

KICS reported a low-severity condition on the assessed asset. Possible impact: Deployed infrastructure may inherit the reported insecure configuration.

What to do next: Correct the infrastructure-as-code template so redeployment does not restore the insecure setting.

How to confirm the fix: Rerun KICS with the same scope after the change and confirm that “Healthcheck Instruction Missing” is no longer reported.

Official scanner references: https://docs.docker.com/engine/reference/builder/#healthcheck · https://github.com/Checkmarx/kics · https://www.kics.io/

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-21a58716ec4c5fbd166bd9a7480bb494

Why this priority

Evidence SHA-256

Related framework references

Vulnerable package flask 3.0.3 (CVE-2026-27205 / GHSA-68rp-wp8r-4726) — Asset 1

Low · 2 original findings

A container or software component may expose the workload to a known weakness.

Target: Asset 1

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Related checks (2)

Vulnerable package flask (GHSA-68rp-wp8r-4726) — Asset 1

Severity: LowConfidence: MediumPriority: 35Report order #14Suggested expert: Software supply-chain engineer

Grype reported a low-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 3.1.3

How to confirm the fix: Rerun Grype with the same scope after the change and confirm that source rule GHSA-68rp-wp8r-4726 is no longer reported.

Official scanner references: https://github.com/advisories/GHSA-68rp-wp8r-4726 · https://github.com/anchore/grype · https://github.com/pallets/flask/commit/089cb86dd22bff589a4eafb7ab8e42dc357623b4 · https://github.com/pallets/flask/releases/tag/3.1.3 · https://github.com/pallets/flask/security/advisories/GHSA-68rp-wp8r-4726 · https://nvd.nist.gov/vuln/detail/CVE-2026-27205

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-d238d1da88589599818f5ac99b0acdc7

Why this priority

  • Source severity: Low
  • Confidence derived from an installed-version match against a published advisory range; Grype reports no confidence of its own.

Evidence SHA-256

  • 8ea94f90312ba26c32607ea526ba7e3b06881ffe1fb22abb63fb8b9e30316680
    Evidence evidence-6354069063d5ca523db04b8ffaaa2ec4 · Check grype · Observed 2026-10-07 01:37:52 UTC
    Source rule
    GHSA-68rp-wp8r-4726
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    61b950c1-ddf7-4e28-b77c-8f59ce9b926a
    Artifact ID
    0699b40c-764b-4284-970f-57b74f63d374
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    3.0.3
    Scanner-provided fixed version
    3.1.3
    Scanner-reported CVSS
    2.3 · v4.0 · scored by grype
    CVSS vector
    CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Related framework references

  • The packaged mapping catalog has no entry for this finding's rule, so its framework position is unknown, not absent.

flask: Flask: Information disclosure via improper caching of session data — Asset 1

Severity: LowConfidence: MediumPriority: 35Report order #15Suggested expert: Software supply-chain engineer

Trivy reported a low-severity condition on the assessed asset. Possible impact: A container or software component may expose the workload to a known weakness.

What to do next: Upgrade the affected component to a fixed version; if none is available, record the blocker and track the fix.

Scanner-provided fixed version: 3.1.3

How to confirm the fix: Rerun Trivy with the same scope after the change and confirm that source rule CVE-2026-27205 is no longer reported.

Official scanner references: https://access.redhat.com/security/cve/CVE-2026-27205 · https://avd.aquasec.com/nvd/cve-2026-27205 · https://github.com/aquasecurity/trivy · https://github.com/pallets/flask · https://github.com/pallets/flask/commit/089cb86dd22bff589a4eafb7ab8e42dc357623b4 · https://github.com/pallets/flask/releases/tag/3.1.3 · https://github.com/pallets/flask/security/advisories/GHSA-68rp-wp8r-4726 · https://nvd.nist.gov/vuln/detail/CVE-2026-27205 · https://trivy.dev/ · https://ubuntu.com/security/notices/USN-8104-1 · https://www.cve.org/CVERecord?id=CVE-2026-27205

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-ea18147c591cf6eeec191b9d63c2b4a8

Why this priority

  • Source severity: LOW
  • Confidence derived from an installed-version match against a published advisory range; Trivy reports no confidence of its own.

Evidence SHA-256

  • 95af5c40a8cd3504bc9fd07b9db2846db951574326518d58a803aaada8a948a2
    Evidence evidence-43d931171a5b5a8e4036b8da18be7811 · Check trivy · Observed 2026-10-07 01:35:28 UTC
    Source rule
    CVE-2026-27205
    Evidence summary
    [redacted evidence summary]
    Evidence kind
    Package Inventory
    Engine run ID
    00707d6c-ca99-4ddd-9708-8a4e2aa0b30b
    Artifact ID
    afa6f00a-3bce-4b71-ac77-d936a6848cb9
    Result pointer
    [redacted result pointer]
    Evidence location
    [redacted location]

    Scanner-provided details

    Scanner-provided description
    [redacted scanner-provided description]
    Scanner-provided installed version
    3.0.3
    Scanner-provided fixed version
    3.1.3
    Scanner-assigned CWE
    CWE-524
    Scanner-reported CVSS
    4.3 · v3.1 · scored by nvd
    CVSS vector
    CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
    Scanner-reported CVSS
    4.3 · v3.1 · scored by redhat
    CVSS vector
    CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N

Related framework references

  • ISO/IEC 27001 2022 / A.8.8 — Technical vulnerability handling
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • NIST CSF 2.0 / ID.RA-01 — Vulnerability identification and recording
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.
  • OWASP Top 10 2021 / A06:2021 — Vulnerable and Outdated Components
    Relationship: related
    Why related: Evidence that an installed component is affected by a CVE is related to vulnerability handling. For an AI system, AIDEFEND separates build or deployment admission from the deployed-software remediation lifecycle; this reference does not decide which lifecycle state applies.

Ensure that HEALTHCHECK instructions have been added to container images — Asset 1

Severity: UnknownConfidence: HighPriority: 20Report order #16Suggested expert: Infrastructure-as-code engineer

Checkov reported this condition without a severity rating. Severity is Unknown. Possible impact: Deployed infrastructure may inherit the reported insecure configuration.

What to do next: Correct the infrastructure-as-code template so redeployment does not restore the insecure setting.

How to confirm the fix: Rerun Checkov with the same scope after the change and confirm that source rule CKV_DOCKER_2 is no longer reported.

Official scanner references: https://github.com/bridgecrewio/checkov · https://www.checkov.io/

Evidence and framework references

Selected-run source: Saved result from this run · Finding ID: finding-38e43d6117d5c77fdf7a0e58a51dcc29

Why this priority

Evidence SHA-256

Related framework references

Inventory observations

Inventory observations are separate from vulnerability findings and remediation priorities.

Total: 3 · Services: 0 · Software components: 3 · Cloud resources: 0 · Inventoried assets: 1 · Representative records: 3

Inventoried asset list: Asset 1

Representative sample (maximum 3)

Complete inventory by asset

Asset 1 asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

  • Software component — Name [redacted software component] · version [redacted version] · package type python · purl [redacted purl]
    Source provenance
    • Observation inventory-bd795e8f9a1b3df17a0f1fcd014398f0 · engine syft · engine run 8b37c836-6daa-4599-8c11-748ddabc2f66
      artifact d372c572-a99a-46e0-9c58-3b0b049ed65f · SHA-256 58219fba9a0aed8478a80fb7c5b2e22c8be957086301886f824eadf7f1d7ae68
      pointer [redacted inventory pointer] · observed 2026-10-07 01:38:03 UTC
  • Software component — Name [redacted software component] · version [redacted version] · package type python · purl [redacted purl]
    Source provenance
    • Observation inventory-6b3c1f1dc1e4e3b4521995d96fab7d73 · engine syft · engine run 8b37c836-6daa-4599-8c11-748ddabc2f66
      artifact d372c572-a99a-46e0-9c58-3b0b049ed65f · SHA-256 58219fba9a0aed8478a80fb7c5b2e22c8be957086301886f824eadf7f1d7ae68
      pointer [redacted inventory pointer] · observed 2026-10-07 01:38:03 UTC
  • Software component — Name [redacted software component] · version [redacted version] · package type python · purl [redacted purl]
    Source provenance
    • Observation inventory-1bbbc5120db2805b6d2f78d41d455f9c · engine syft · engine run 8b37c836-6daa-4599-8c11-748ddabc2f66
      artifact d372c572-a99a-46e0-9c58-3b0b049ed65f · SHA-256 58219fba9a0aed8478a80fb7c5b2e22c8be957086301886f824eadf7f1d7ae68
      pointer [redacted inventory pointer] · observed 2026-10-07 01:38:03 UTC

Where this lands in each framework

Each reference below was reached from a finding's own rule or CWE through the packaged mapping catalog. They are navigation aids for finding the relevant control text, not a compliance result: nothing here is an audit, a certification, or a pass.

FrameworkWhat this run showsControlsFindings
NIST CSF
version 2.0		Related references observed25
ISO/IEC 27001
version 2022		Related references observed35
AIDEFEND
version 1.20260805		Unknown — the context answers are incomplete00
OWASP Top 10
version 2021		Related references observed49
OWASP Top 10 for LLM Applications
version 2025		Unknown — the context answers are incomplete00
CIS Kubernetes Benchmark
version 1.11		Unknown — coverage is incomplete00
CIS Amazon Web Services Foundations Benchmark
version 3.0.0		Unknown — coverage is incomplete00

AIDEFEND version 1.20260805, OWASP Top 10 for LLM Applications version 2025 — No reference to this AI-specific framework was inferred because at least one required AI-context answer is legacy or unanswered. This remains unknown, not not-applicable.

CIS Kubernetes Benchmark version 1.11, CIS Amazon Web Services Foundations Benchmark version 3.0.0 — No related reference was observed, but coverage is incomplete or unknown. This cannot be interpreted as a passed or implemented control.

NIST CSF version 2.0

Related references observed

ControlTitleFindingsSeverity mix
ID.RA-01Vulnerability identification and recording4

Medium 3 · Low 1

PR.PS-06Secure software development practices1

High 1

ISO/IEC 27001 version 2022

Related references observed

ControlTitleFindingsSeverity mix
A.8.8Technical vulnerability handling4

Medium 3 · Low 1

A.8.28Secure coding practices1

High 1

A.8.29Security testing before acceptance1

High 1

OWASP Top 10 version 2021

Related references observed

ControlTitleFindingsSeverity mix
A01:2021Broken Access Control1

Medium 1

A03:2021Injection5

High 5

A04:2021Insecure Design1

Medium 1

A06:2021Vulnerable and Outdated Components4

Medium 3 · Low 1

Framework sources and attribution

NIST CSF version 2.0 — NIST Cybersecurity Framework (CSF) 2.0, National Institute of Standards and Technology. Use of NIST source material remains subject to the source publication's notices. Framework relationships and rationales in this report are project-authored navigation metadata. NIST has not reviewed or endorsed this report or integration. https://doi.org/10.6028/NIST.CSWP.29

ISO/IEC 27001 version 2022 — ISO/IEC 27001:2022 control coordinates are referenced nominatively. ISO/IEC standard content remains subject to ISO's terms; this report is not a copy of the standard. Framework relationships and rationales in this report are project-authored navigation metadata. ISO and IEC have not reviewed or endorsed this report or integration. https://www.iso.org/standard/27001

AIDEFEND version 1.20260805 — AIDEFEND AI Defense Framework, created by Edward Lee, https://aidefend.net, licensed under CC BY 4.0. Creative Commons Attribution 4.0 International: https://creativecommons.org/licenses/by/4.0/ ai-security-scanner uses a modified, project-authored six-record metadata selection from AIDEFEND 1.20260805 at pinned commit e10c1678ee49f03f8fb0c97d446ba3fbc3543655. This independent integration is not affiliated with, approved, certified, sponsored, or endorsed by AIDEFEND or its owner. https://github.com/edward-playground/aidefense-framework/blob/e10c1678ee49f03f8fb0c97d446ba3fbc3543655/data/data.json

OWASP Top 10 version 2021 — OWASP Top 10:2021, Copyright (c) 2003-2025 The OWASP Foundation, Inc., licensed under CC BY-SA 4.0. Creative Commons Attribution-ShareAlike 4.0 International: https://creativecommons.org/licenses/by-sa/4.0/ Category membership is read from the CWE sets OWASP publishes for each 2021 category; the rationales beside them are project-authored navigation metadata. The OWASP Foundation has not reviewed or endorsed this report or integration. https://owasp.org/Top10/

OWASP Top 10 for LLM Applications version 2025 — OWASP Top 10 for LLM Applications 2025, OWASP GenAI Security Project, Copyright (c) The OWASP Foundation, Inc., licensed under CC BY-SA 4.0. Creative Commons Attribution-ShareAlike 4.0 International: https://creativecommons.org/licenses/by-sa/4.0/ This report references three of the ten 2025 categories, the only ones the packaged engines produce evidence for; the rationales are project-authored navigation metadata. The OWASP Foundation and the OWASP GenAI Security Project have not reviewed or endorsed this report or integration. https://genai.owasp.org/llm-top-10/

CIS Kubernetes Benchmark version 1.11 — CIS Kubernetes Benchmark v1.11 recommendation numbers and titles are referenced nominatively; they are the coordinates kube-bench itself reports against. CIS Benchmark content remains subject to the Center for Internet Security's terms of use; this report is not a copy of the benchmark. Recommendation titles are reproduced as the pinned kube-bench image reports them. The Center for Internet Security has not reviewed or endorsed this report or integration. https://www.cisecurity.org/benchmark/kubernetes

CIS Amazon Web Services Foundations Benchmark version 3.0.0 — CIS Amazon Web Services Foundations Benchmark v3.0.0 recommendation numbers and titles are referenced nominatively. CIS Benchmark content remains subject to the Center for Internet Security's terms of use; this report is not a copy of the benchmark. The recommendation-to-check relationship is the one Prowler publishes in its own CIS 3.0 compliance file. The Center for Internet Security has not reviewed or endorsed this report or integration. https://www.cisecurity.org/benchmark/amazon_web_services

Technical details

Exact requested identities

Target IDs

Check IDs

Selected-run task details

Redacted diagnostic log

Every task in this run recorded the same state.

Availability: Unavailable
Run-bound diagnostic log: unavailable. Redacted diagnostic export: separate.

Scanner messages are not included in this readable HTML report.

Task 00707d6c-ca99-4ddd-9708-8a4e2aa0b30b

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:35:28 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine trivy; adapter 0.2.6; engine version 0.74.0; last updated 2026-08-24; image repository ghcr.io/teddashh/ai-security-scanner-engine-trivy; image sha256:9bfcef9a6a9d9a69eefcece06b0670eaed72541656b65155469b41acb3855dc2; command SHA-256 fd202ea65d8acd07cdca370a1569531b92eb306148db6a19df23270c73618540; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules e1fd17a0ea4a8cf24bc4b4dd7e2cfbf4bb31b994

Evidence SHA-256

Task 1f08d2b6-3ab4-4cd2-9ed7-735224759ca9

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:36:49 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine checkov; adapter 0.2.6; engine version 3.3.13; last updated 2026-08-24; image repository ghcr.io/teddashh/ai-security-scanner-engine-checkov; image sha256:0ecc187b17faa9c538c9b1ecc08a4195283290222694d0f87d50016f2bb79b35; command SHA-256 e4c81c7a215769616f0e68122333d6ceee3db3aebfc085861b8488e013ca2bf1; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules 0604e97b0f77c89a8c6c1fe2219c3d251cbb9789

Evidence SHA-256

Task 40dca26d-1da9-4dc5-8244-f8d7c1d5da9e

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:35:58 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine kics; adapter 0.2.6; engine version 2.1.20; last updated 2026-08-24; image repository checkmarx/kics; image sha256:3e5a268eb8adda2e5a483c9359ddfc4cd520ab856a7076dc0b1d8784a37e2602; command SHA-256 d0194e28734693b5ecdd5dfb8700979035a4ba6a55847c93e6be0e7a40aa1d01; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules e1f23cad9640f55b963f22a116b04906b8c16ac6

Evidence SHA-256

Task 61b950c1-ddf7-4e28-b77c-8f59ce9b926a

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:37:53 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine grype; adapter 0.2.6; engine version 0.117.0; last updated 2026-08-24; image repository ghcr.io/teddashh/ai-security-scanner-engine-grype; image sha256:56b0d675e3b8d539890e853699c114493a72a54cca0bbe254eceee7ec2b4c517; command SHA-256 4f696152031992a5af1d4a3dac05cc5699bd3c2da3aa188ff5571a3053cb9067; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules b5fa92bbcbef655497e3be840a2f718380e2cdd3

Evidence SHA-256

Task 8b37c836-6daa-4599-8c11-748ddabc2f66

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:38:04 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine syft; adapter 0.2.6; engine version 1.51.0; last updated 2026-08-24; image repository ghcr.io/teddashh/ai-security-scanner-engine-syft; image sha256:805c9fe522113319f994f99cd68fcb5c18e322dd933e7d89f82cd91f5a5c8501; command SHA-256 a8c38b73e0b1e3e95fc043d1554adba51ef64d4eec964a87fb179865ce4d14b5; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules 2293641e3bd628a01bb37639318d62c0ebe89b39

Evidence SHA-256

Task c7703a88-d74d-408c-b84e-c28d28a7b16d

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:26:59 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine gitleaks; adapter 0.2.6; engine version 8.30.1; last updated 2026-08-24; image repository ghcr.io/teddashh/ai-security-scanner-engine-gitleaks; image sha256:95313654f9c37115a906629a82113ba6e1c729950be70909da8362e9482b477e; command SHA-256 76d7d6583c581bada2a5cf02eeda810a3856756e152bb5bbdb7f73dc1bd3c0f0; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules sha256:e163e53b9e7e8a8511e77271e2b323ed057759542a6d988258afe3a1fa329caf

Evidence SHA-256

Task ddfbdd4f-3c68-4f42-9af7-2eb64f6fecd4

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:34:58 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine semgrep; adapter 0.2.6; engine version 1.174.0 (source@a0c13f304151e531c7e7c00838076211a07a790c); last updated 2026-08-24; image repository ghcr.io/teddashh/ai-security-scanner-engine-semgrep; image sha256:3f1a10c7bce32eae912479c5744dbb653bdfa9a4cbd3d53afd2e0a435b10fb59; command SHA-256 e8957f5e89fd6d47b138eb49c8548af09d5a7da3f26dd09ab6b8fdf6f92bd188; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules 0f5a85ceab1b82b193d0eaa418784c932d237d68

Evidence SHA-256

Task e74cb844-9c96-4001-a61c-cb4d67ee1c9e

State: Completed · Progress: 100%

Started: 2026-10-07 01:26:25 UTC · Finished: 2026-10-07 01:35:43 UTC · Targets: asset-workspace-source-ce6e9c1d-53d1-4bf2-853f-774361bdb818

Exit code: 0 · Error code: none recorded · Cleanup: removed=true

Execution identity: engine trufflehog; adapter 0.2.6; engine version 3.97.0 (source@3ab759fef4bb5935d4fe9ac68b503d05346b8364); last updated 2026-08-24; image repository ghcr.io/teddashh/ai-security-scanner-engine-trufflehog; image sha256:dd0e0879bc4d3ac79194d6c734d2a2636cc83fdacb01f611b6b3284fe86dd55a; command SHA-256 87559bf62666b22b4d5687211deeb33c256ee3b901a232718fe85f84eacfb67a; runtime managed_local; runtime version 5.8.2; runtime security {"apparmorEnabled":false,"capabilities":"CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT","rootless":true,"seccompEnabled":true,"seccompProfilePath":"/usr/share/containers/seccomp.json","selinuxEnabled":true}; distribution Pull Pinned Image; rules 3ab759fef4bb5935d4fe9ac68b503d05346b8364

Evidence SHA-256

Report data-quality notes

Reversible finding groups

Groups are presentation metadata only. Every canonical finding, fingerprint, evidence record, and raw artifact remains independent; removing a group appends history and does not delete its members.

No active presentation groups are recorded.

Immutable grouping history

TimeActionGroup IDTitleFinding IDsReasonActor
No grouping events are recorded.