What is the official website of Zurich Community Trust ?

The official website of Zurich Community Trust is https://www.zct.org.uk/.

What is Zurich Community Trust's cybersecurity risk score?

Zurich Community Trust has an AI-generated cybersecurity risk score of 755 out of 1000, indicating a Fair security posture according to Rankiteo's assessment.

How many security incidents has Zurich Community Trust experienced?

According to Rankiteo, Zurich Community Trust currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.

Has Zurich Community Trust been affected by any supply chain cyber incidents ?

According to Rankiteo, Zurich Community Trust has not been affected by any supply chain cyber incidents, and no incident IDs are currently listed for the organization.

Does Zurich Community Trust have SOC 2 Type 1 certification ?

According to Rankiteo, Zurich Community Trust is not certified under SOC 2 Type 1.

Does Zurich Community Trust have SOC 2 Type 2 certification ?

According to Rankiteo, Zurich Community Trust does not hold a SOC 2 Type 2 certification.

Does Zurich Community Trust comply with GDPR ?

According to Rankiteo, Zurich Community Trust is not listed as GDPR compliant.

Does Zurich Community Trust have PCI DSS certification ?

According to Rankiteo, Zurich Community Trust does not currently maintain PCI DSS compliance.

Does Zurich Community Trust comply with HIPAA ?

According to Rankiteo, Zurich Community Trust is not compliant with HIPAA regulations.

Does Zurich Community Trust have ISO 27001 certification ?

According to Rankiteo,Zurich Community Trust is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.

Which industry does Zurich Community Trust operate in ?

Zurich Community Trust operates primarily in the Non-profit Organization Management industry.

How many employees does Zurich Community Trust have ?

Zurich Community Trust employs approximately None employees people worldwide.

Does Zurich Community Trust own any subsidiaries ?

Zurich Community Trust presently has no subsidiaries across any sectors.

How many LinkedIn followers does Zurich Community Trust have ?

Zurich Community Trust's official LinkedIn profile has approximately 1,530 followers.

Does Zurich Community Trust have a Crunchbase profile ?

No, Zurich Community Trust does not have a profile on Crunchbase.

Does Zurich Community Trust have a LinkedIn profile ?

Yes, Zurich Community Trust maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/zurich-community-trust.

How many cybersecurity incidents has Zurich Community Trust experienced ?

As of August 8, 2026, Rankiteo reports that Zurich Community Trust has experienced 2 cybersecurity incidents.

How many peer or competitor companies does Zurich Community Trust have ?

Zurich Community Trust has an estimated 5,259 peer or competitor companies worldwide.

What types of cybersecurity incidents has Zurich Community Trust faced ?

Incident Types: The types of cybersecurity incidents that have occurred include Data Leak and Breach.

NEWRankiteo Cyber Underwriting Desktop - Score, price, and bind from your desktop

WindowsmacOSLinux

Download

Badge your company to reduce your risk score and your cyber insurance costs!

Link verified badges to your company page to build trust with insurers and customers.

Apply now and get your badge!

Internal validation & live display

Insurers and partners see a safer profile

Faster underwriting decisions

Trusted by insurers. Chosen by leaders.

Proud contributor to the Society of Actuaries.

ZCT

Boost Score +25 with badge (5 left)

755

/1000

Fair

780

/1000

Fair

Zurich Community Trust Vendor Cyber Rating & Cyber Score

zct.org.uk

Add Your Compliance Badge

The Zurich Community Trust provides Zurich UK employees with engagement opportunities through our charity partnerships and programmes. Since we launched in 1973, we've awarded over £100 million to causes all over the UK and overseas. Charity no: 266983.

ZCT A.I CyberSecurity Scoring

Scoring History

ZCT

Zurich Community Trust CyberSecurity News & History

Past Incidents

Attack Types

Entity

Type

Severity

Impact

Seen

Blog Details

Supply Chain Source

Incident Details

View

Zurich Community Tr...

Data Leak

8/2021

ZUR024131222

Zurich Community Tr...

Breach

8/2018

ZUR408072725

Loading…

A.I.

ZCT Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Actual

Prediction

Incident Predictions locked

Access Monitoring Plan

A.I Risk Score Likelihood 3 - 6 - 9 months

Actual

Prediction A

Prediction B

Prediction C

Prediction D

A.I. Risk Score Predictions locked

Access Monitoring Plan

Loading…

Underwriter Stats for ZCT

Incidents vs Non-profit Organization Management Industry Avg (This Year)

No incidents recorded for Zurich Community Trust in 2026.

Incidents vs All-Companies Average (This Year)

No incidents recorded for Zurich Community Trust in 2026.

Incident Types ZCT vs Non-profit Organization Management Industry Avg (This Year)

No incidents recorded for Zurich Community Trust in 2026.

Incident History - ZCT (X = Date, Y = Severity)

Loading…

SUBSIDIARY

Zurich Community Trust Subsidiaries

ZCT

Non-profit Organization Management

Website: https://www.zct.org.uk/

Company Size: 11-50 employees

Zurich InsuranceInsurance

Zurich North AmericaInsurance

Zurich New ZealandInsurance

Zurich MunicipalFinancial Services

Zurich AdviserInsurance

Loading…

Zurich Community Trust Similar Companies

Loading…

NEWS

Zurich Community Trust CyberSecurity News

Latest updates, reports, and threat intel affecting the global network.

December 15, 2025 07:42 AM

Zurich-based Soverli raises €2.2 million to bring sovereign security to everyday smartphones

Zurich-based cybersecurity company Soverli has raised €2.2 million ($2.6 million) in pre-Seed funding to introduce a sovereign smartphone...

Read Article

Loading…

CVE

Latest

Global CVEs (Not Company-Specific)

CVE-2026-52880

SUMMARY

Klever-Go is the Go implementation of the Klever blockchain protocol. Versions from 1.7.14 through 1.7.17 are vulnerable to a remotely triggerable denial of service. Both REST APIs are started with the Gin Engine.Run convenience method, which serves requests through Go's default HTTP server with no ReadHeaderTimeout, ReadTimeout, or MaxHeaderBytes configured. As a result, incoming connections that never complete their request headers are held open indefinitely. When a REST listener is reachable beyond localhost through the documented all-interface bind or a Docker port-publish deployment, a single unauthenticated client can open many slow-header connections and hold them open until server file descriptors are exhausted, preventing the API from accepting new connections. This renders the REST API unavailable to legitimate clients. This issue is fixed in version 1.7.18.

Published

Date2026-08-07

Updated

Date2026-08-07

RISK INFORMATION (Score: 7.5)

cvss3

Base Score: 7.5

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

3.9

REFERENCES

CVE-2026-52879

SUMMARY

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions 1.7.14 through 1.7.17, the direct-message ingress handler spawns a new goroutine for every incoming direct message before the processor-level antiflood layer makes any admission decision, with no semaphore, throttler, or bound on the number of concurrent in-flight spawns. Because the antiflood check runs inside the spawned goroutine rather than before it, a single connected peer can open a direct-send stream and send a stream of well-formed messages to force unbounded goroutine creation, where each goroutine allocates its own stack and holds a message reference until processing completes, adding scheduler and garbage-collection pressure faster than the runtime can drain it. This lets one peer degrade the node's availability and its ability to process legitimate traffic, resulting in a remotely triggerable denial of service. The issue is fixed in 1.7.18.

Published

Date2026-08-07

Updated

Date2026-08-07

RISK INFORMATION (Score: 7.5)

cvss3

Base Score: 7.5

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

3.9

REFERENCES

CVE-2026-52878

SUMMARY

Klever-Go is the Go implementation of the Klever blockchain protocol. Versions 1.7.14 through 1.7.17 are vulnerable to a nil-pointer panic triggered by a protobuf Transaction whose embedded RawData sub-message is omitted. This omission causes RawData to decode to nil. Every transaction gossiped on the Klever-Go P2P network is decoded and validated synchronously inside the libp2p pubsub topic-validator callback, where txVersionChecker.CheckTxVersion dereferences tx.RawData.Version with no nil check. Because the libp2p pubsub callback, the underlying go-libp2p-pubsub validation worker, and Klever's own network/p2p layer install no recover(), the panic propagates and crashes the entire node process. The attacker payload is a 3-byte protobuf message; no validator key, stake, funds, or on-chain account is required, and delivery aimed at enough of the BLS validator set can halt block production, resulting in a chain halt. This issue has been fixed in version 1.7.18.

Published

Date2026-08-07

Updated

Date2026-08-07

RISK INFORMATION (Score: 7.5)

cvss3

Base Score: 7.5

Complexity: LOW

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

3.9

REFERENCES

CVE-2026-49343

SUMMARY

Klever-Go is the Go implementation of the Klever blockchain protocol. In versions prior to 1.7.18, the account-data trie syncers are vulnerable to a resource-exhaustion flaw that leaks bounded throttler slots on error paths. In syncDataTrie() (in both userAccountsSyncer.go and kappAccountsSyncer.go), StartProcessing() reserves a slot from the NumGoRoutinesThrottler, but the corresponding EndProcessing() is only called on the success path and on the duplicate-root early return. As a result, any error from trie.NewTrie(), trie.NewTrieSyncer(), or trieSyncer.StartSyncing() (including the network-dependent timeout path) permanently consumes one slot for the lifetime of the throttler. An attacker who can repeatedly cause trie-node sync failures or timeouts during bootstrap can exhaust the bounded throttler, after which further account-data trie syncs stop making progress and SyncAccounts() returns a timeout. Because epoch bootstrap in syncUserAccountsState() and syncKappAccountsState() aborts on any such error, this causes bootstrap to fail, a core availability issue affecting fresh, restarting, or resyncing nodes and validators. This issue is fixed in version 1.7.18.

Published

Date2026-08-07

Updated

Date2026-08-07

RISK INFORMATION (Score: 5.9)

cvss3

Base Score: 5.9

Complexity: HIGH

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Impact Score

3.6

Exploitability

2.2

REFERENCES

CVE-2026-48122

SUMMARY

Ruby LSP is an implementation of the language server protocol for Ruby. Several workspace-level settings in the Ruby LSP VS Code extension prior to version 0.10.4 could override the path to the Ruby executable, the version manager executables, or the Bundler `Gemfile` used at startup. A malicious repository containing a `.vscode/settings.json` could set these values to attacker-controlled targets. Opening and trusting the repository would then execute code with the privileges of the developer. The Ruby LSP gem and clients of the language server in other editors are not affected. Version 0.10.4 of the Ruby LSP VS Code extension fixes the issue.

Published

Date2026-08-07

Updated

Date2026-08-07

RISK INFORMATION (Score: )

cvss4

Base Score: 5.4

Complexity: LOW

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Impact Score

Exploitability

REFERENCES

https://github.com/Shopify/ruby-lsp/security/advisories/GHSA-2x7g-8mp4-572w

Loading…

API

Access Data Using Our API

Get company history

curl -i -X GET 'https://api.rankiteo.com/underwriter-getcompany-history?
linkedin_id=axa' -H 'apikey: YOUR_API_KEY_HERE'

Try It API Documentation Rapid

MEASURE

What Do We Measure ?

Incident

Finding

Grade

Digital Assets

Every week, Rankiteo analyzes billions of signals to give organizations a sharper, faster view of emerging risks. With deeper, more actionable intelligence at their fingertips, security teams can outpace threat actors, respond instantly to Zero-Day attacks, and dramatically shrink their risk exposure window.

These are some of the factors we use to calculate the overall score:

Network SecurityIdentify exposed access points, detect misconfigured SSL certificates, and uncover vulnerabilities across the network infrastructure.

SBOM (Software Bill of Materials)Gain visibility into the software components used within an organization to detect vulnerabilities, manage risk, and ensure supply chain security.

CMDB (Configuration Management Database)Monitor and manage all IT assets and their configurations to ensure accurate, real-time visibility across the company's technology environment.

Threat IntelligenceLeverage real-time insights on active threats, malware campaigns, and emerging vulnerabilities to proactively defend against evolving cyberattacks.

Rankiteo

By Rankiteo

★ ★ ★ ★ ★

View on G2.com

Rankiteo is a unified scoring and risk platform that analyzes billions of signals weekly to help organizations gain faster, more actionable insights into emerging threats. Empowering teams to outpace adversaries and reduce exposure.

View latest plans →View all security reports →

MILESTONEG

Users
Love Us

Loading…