PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-97879 zhistaredu CVE debrief

A security flaw has been discovered in zhistaredu StarTraining up to 3.8.1. The affected element is an unknown function of the file SecurityConfig.java of the component api-docs Endpoint. Performing a manipulation results in missing authentication. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

Vendor
zhistaredu
Product
StarTraining
CVSS
MEDIUM 5.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-25
Original CVE updated
2026-09-25
Advisory published
2026-09-25
Advisory updated
2026-09-25

Who should care

Defenders responsible for zhistaredu StarTraining deployments should assess exposure and prioritize verification of affected versions. This includes reviewing authentication mechanisms for the api-docs Endpoint and implementing compensating controls for remote attacks. Security teams and vulnerability management teams should also review the affected scope and severity to ensure proper mitigation and remediation.

Why it matters

Defenders should prioritize verifying the presence of affected versions and assessing exposure of the api-docs Endpoint due to the risk of remote attacks from missing authentication.

  • Verify authentication mechanisms for api-docs Endpoint
  • Assess exposure of zhistaredu StarTraining deployments
  • Implement compensating controls for remote attacks

Technical summary

The vulnerability is located in the SecurityConfig.java file of the api-docs Endpoint in zhistaredu StarTraining up to 3.8.1. An attacker can perform a manipulation to result in missing authentication, allowing for remote attacks. This could lead to unauthorized access or control of affected systems. Defenders should prioritize verifying the presence of affected versions and assessing exposure of the api-docs Endpoint due to the risk of remote attacks from missing authentication. The exploit has been released to the public and may be used for attacks.

Defensive priority

Defenders should prioritize verifying the presence of affected versions and assessing exposure of the api-docs Endpoint.

Recommended defensive actions

  • Verify the presence of affected versions of zhistaredu StarTraining
  • Assess exposure of the api-docs Endpoint
  • Implement authentication mechanisms for the api-docs Endpoint
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but vendor comments are lacking. The vulnerability is in zhistaredu StarTraining up to 3.8.1, specifically in the SecurityConfig.java file of the api-docs Endpoint. Defenders should verify the presence of affected versions and assess exposure of the api-docs Endpoint. The exploit has been released to the public and may be used for attacks. There is no vendor response to early disclosure.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-97879 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-97879

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-97879 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-97879

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.