Skip to main content

Security Advisories

This page lists vulnerability information and security notices related to Kuroco, together with whether Kuroco is affected and the current response status. For details of each advisory, see the linked notice. This page also shows whether Kuroco uses major software for which many vulnerabilities have been reported.

Advisories​

You can receive new and updated advisories via RSS. When the status of an advisory is updated, it is delivered as a new item.

For the meaning of each status, see Status definitions. For the meaning of each urgency level, see Urgency criteria. Urgency is shown only for vulnerabilities that may affect Kuroco. In the RSS feed, it is shown at the beginning of the title together with the status. For CVSS, EPSS, and CISA KEV shown in the notices, see Vulnerability metrics.

PublishedLast updatedTitleTypeStatusUrgency
2026-11-192026-11-20Response Status for the PHP Security Releases (November 2026)VulnerabilityNot affected-
2026-11-192026-11-19Response Status for Multiple Vulnerabilities in nginx HTTP/2 Processing (CVE-2026-123633, CVE-2026-123007)VulnerabilityNot affected-
2026-11-122026-11-13Response Status for Multiple Vulnerabilities in PostgreSQLVulnerabilityInvestigating-
2026-11-062026-11-06Response Status for the OpenSSH Vulnerability (CVE-2026-123158)VulnerabilityNot affected-
2026-11-062026-11-06Emergency Release: Country Restriction and Per-IP Rate Limit for APIsSecurity enhancementCustomer action recommended-
2026-11-052026-11-12Response Status for the Node.js Security Releases (November 2026)VulnerabilityNot affected-
2026-10-302026-10-30Response Status for Multiple Vulnerabilities in nginx (CVE-2026-15176, CVE-2026-93479, CVE-2026-97205)VulnerabilityNot affected-
2026-10-302026-11-20Response Status for the Linux Kernel Vulnerability (CVE-2026-98432)VulnerabilityNot affected-
2026-10-302026-10-30Response Status for the Out-of-Bounds Write Vulnerability in the C Implementation of Brotli (CVE-2026-111497)VulnerabilityResolved-
2026-10-302026-10-30Response Status for Multiple Vulnerabilities in PHP (CVE-2026-109618, CVE-2026-109619)VulnerabilityResolvedCritical
2026-10-202026-10-20Request to Take Measures Against Unauthorized Admin Panel LoginsNoticeCustomer action recommended-
2026-10-152026-10-15Save Restrictions for Smarty Plugins That Handle Credentials and SecretsSecurity enhancementResolved-
2026-02-242026-04-22Change in Email Two-Factor Authentication Behavior When Email Cannot Be SentSecurity enhancementResolved (applied in the 2026-04-22 stable release)-
2025-04-222025-04-22Access to files attached to members now requires authenticationSecurity enhancementResolved-
2024-04-012024-07-16Implementation of disabling cipher suiteSecurity enhancementResolved (applied in the 2024-07-16 stable release)-
2024-03-302024-04-02Notice on the Impact and Response Status Related to CVE-2024-3094 Affecting KurocoVulnerabilityNot affected-

Usage of major software​

This section shows whether Kuroco uses major software for which many vulnerabilities have been reported. For the response status of vulnerabilities in the software that Kuroco uses, see Advisories.

Major software in use​

SoftwareUsageSecurity advisories
nginxUsednginx Security Advisories
EnvoyUsedEnvoy Security Advisories
PHPUsedPHP Security Advisories
PHP-FPMUsedPHP Security Advisories
PostgreSQLUsedPostgreSQL Security Information
Cloud SQL for PostgreSQL maintenance changelog
Amazon Aurora PostgreSQL updates
RustUsedRustSec Advisory Database
GoUsed for some featuresGo Vulnerability Database
Node.jsUsed for some features (mainly related to KurocoFront) as a Google Cloud managed serviceNode.js Security Releases

Major software not in use​

Kuroco does not use the following software, which we are frequently asked about.

F5 BIG-IP, Fortinet FortiGate (FortiOS), Palo Alto Networks PAN-OS, Ivanti Connect Secure, Citrix NetScaler, Cisco ASA, SonicWall, VMware ESXi / vCenter, Microsoft Exchange Server, Microsoft SharePoint, Windows Server, Apache HTTP Server, Apache Tomcat, Apache Struts, Log4j, Java, Ruby, MongoDB, WordPress, Atlassian Confluence / Jira, MOVEit Transfer, GitLab, OpenSSH

note

This list does not cover all software. For software not listed here, please contact support.

Status definitions​

StatusDescription
InvestigatingWe are investigating whether Kuroco is affected.
AffectedWe have confirmed that Kuroco is affected and are working on a response.
Not affectedWe have confirmed that Kuroco is not affected.
ResolvedThe response on the Kuroco side has been completed.
Customer action recommendedWe recommend that customers take action in their site settings or implementation.

Vulnerability metrics​

Vulnerability notices show the following publicly available metrics for each CVE. These are general assessments of each CVE and do not indicate whether Kuroco is affected. For the impact on Kuroco, see the response status and the status of each notice.

MetricDescriptionProvider
CVSSThe base score from 0.0 to 10.0 indicating the severity of the vulnerability. The CVSS version and the organization that assessed it are shown with the score. The CVSS 4.0 score is shown if available; otherwise, the CVSS 3.1 score is shown. Among the assessments published in NVD, those by organizations other than NIST (such as the product vendor) are preferred.NVD
EPSSThe estimated probability that the vulnerability will be exploited within the next 30 days. "-" is shown when no value has been calculated yet, such as for a newly published CVE.FIRST
CISA KEVWhether the vulnerability is listed in the Known Exploited Vulnerabilities catalog published by the U.S. CISA, which lists vulnerabilities confirmed to be exploited in the wild.CISA

CVEs listed in CISA KEV and CVEs with a CVSS base score of 7.0 or higher are shown. CVEs that have not been scored with CVSS are also shown.

The values are as of the retrieval date stated in each notice. Until the response is complete, the values are retrieved again whenever the notice is updated. The values in notices for which the response is complete are not updated. For the latest values, see the link for each CVE.

Urgency criteria​

For vulnerabilities that may affect Kuroco, we determine the urgency based on the following criteria and apply a fixed version or mitigation accordingly. Whether Kuroco may be affected is determined by comparing the conditions under which the vulnerability applies with Kuroco's configuration.

UrgencyCriteriaApplying a fixed version or mitigation (target)
CriticalKuroco may be affected, and the vulnerability is listed in CISA KEV or has a CVSS base score of 9.0 or higherApplied as soon as possible, regardless of holidays or late-night hours (targeting within a few hours).
HighKuroco may be affected, and the vulnerability has a CVSS base score of 7.0 or higherApplied within one business day.
NormalKuroco may be affected, and none of the above appliesApplied within a few business days.
Not affectedKuroco is not affectedIf a fixed version is available, it is applied within a few business days.

The times in the table are targets. If what is needed for the application is not available, such as when no fixed version has been released, it may not be possible to apply it within the target time. In that case, we limit the impact with interim measures such as mitigations, and apply the fixed version as soon as it is released.

For business days, see Support hours.

Contact​

If you want to check whether Kuroco is affected by a vulnerability that is not listed here, please contact Kuroco support. Requests to check lists of CVEs that you send us periodically are quoted separately. For details, see Can I check whether Kuroco is affected by a specific vulnerability (CVE) or uses specific software?.


Support

If you have any other questions, please contact us or check out Our Slack Community.