What is the official website of Jungheinrich (ČR) s.r.o. ?

The official website of Jungheinrich (ČR) s.r.o. is http://www.jungheinrich.cz.

What is Jungheinrich (ČR) s.r.o.'s cybersecurity risk score?

Jungheinrich (ČR) s.r.o. 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 Jungheinrich (ČR) s.r.o. experienced?

According to Rankiteo, Jungheinrich (ČR) s.r.o. currently holds 0 security badges, indicating that no recognized compliance certifications are currently verified for the organization.

Has Jungheinrich (ČR) s.r.o. been affected by any supply chain cyber incidents ?

According to Rankiteo, Jungheinrich (ČR) s.r.o. has not been affected by any supply chain cyber incidents, and no incident IDs are currently listed for the organization.

Does Jungheinrich (ČR) s.r.o. have SOC 2 Type 1 certification ?

According to Rankiteo, Jungheinrich (ČR) s.r.o. is not certified under SOC 2 Type 1.

Does Jungheinrich (ČR) s.r.o. have SOC 2 Type 2 certification ?

According to Rankiteo, Jungheinrich (ČR) s.r.o. does not hold a SOC 2 Type 2 certification.

Does Jungheinrich (ČR) s.r.o. comply with GDPR ?

According to Rankiteo, Jungheinrich (ČR) s.r.o. is not listed as GDPR compliant.

Does Jungheinrich (ČR) s.r.o. have PCI DSS certification ?

According to Rankiteo, Jungheinrich (ČR) s.r.o. does not currently maintain PCI DSS compliance.

Does Jungheinrich (ČR) s.r.o. comply with HIPAA ?

According to Rankiteo, Jungheinrich (ČR) s.r.o. is not compliant with HIPAA regulations.

Does Jungheinrich (ČR) s.r.o. have ISO 27001 certification ?

According to Rankiteo,Jungheinrich (ČR) s.r.o. is not certified under ISO 27001, indicating the absence of a formally recognized information security management framework.

Which industry does Jungheinrich (ČR) s.r.o. operate in ?

Jungheinrich (ČR) s.r.o. operates primarily in the Mechanical Or Industrial Engineering industry.

How many employees does Jungheinrich (ČR) s.r.o. have ?

Jungheinrich (ČR) s.r.o. employs approximately 105 people worldwide.

Does Jungheinrich (ČR) s.r.o. own any subsidiaries ?

Jungheinrich (ČR) s.r.o. presently has no subsidiaries across any sectors.

How many LinkedIn followers does Jungheinrich (ČR) s.r.o. have ?

Jungheinrich (ČR) s.r.o.'s official LinkedIn profile has approximately 2,467 followers.

Does Jungheinrich (ČR) s.r.o. have a Crunchbase profile ?

No, Jungheinrich (ČR) s.r.o. does not have a profile on Crunchbase.

Does Jungheinrich (ČR) s.r.o. have a LinkedIn profile ?

Yes, Jungheinrich (ČR) s.r.o. maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/jungheinrich-čr.

How many cybersecurity incidents has Jungheinrich (ČR) s.r.o. experienced ?

As of July 20, 2026, Rankiteo reports that Jungheinrich (ČR) s.r.o. has not experienced any cybersecurity incidents.

How many peer or competitor companies does Jungheinrich (ČR) s.r.o. have ?

Jungheinrich (ČR) s.r.o. has an estimated 2,116 peer or competitor companies worldwide.

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.

Boost Score +25 with badge (5 left)

755

/1000

Fair

780

/1000

Fair

Jungheinrich (ČR) s.r.o. Vendor Cyber Rating & Cyber Score

jungheinrich.cz

Add Your Compliance Badge

Společnost Jungheinrich vyvíjí a vyrábí vybavení pro intralogistiku již více než 65 let. Jsme rodinou firmou s vlastním zastoupením ve více než 40 zemích světa a 17.000 zaměstnanci. V České republice působíme od roku 1992 a jsme dlouhodobě jedničkou na trhu manipulační techniky v počtu dodaných strojů. Na našich pobočkách v Praze, Olomouci a Mladé Boleslavi pracuje přes 350 zaměstnanců. Ochrana osobních údajů: https://www.jungheinrich.cz/ochrana-osobnich-udaju-607348 Impressum: https://www.jungheinrich.cz/impressum-491592

JS A.I CyberSecurity Scoring

Scoring History

Jungheinrich (ČR) s.r.o. CyberSecurity News & History

Past Incidents

Attack Types

Entity

Type

Severity

Impact

Seen

Blog Details

Supply Chain Source

Incident Details

View

No data available

Loading…

A.I.

JS 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 JS

Incidents vs Mechanical Or Industrial Engineering Industry Avg (This Year)

No incidents recorded for Jungheinrich (ČR) s.r.o. in 2026.

Incidents vs All-Companies Average (This Year)

No incidents recorded for Jungheinrich (ČR) s.r.o. in 2026.

Incident Types JS vs Mechanical Or Industrial Engineering Industry Avg (This Year)

No incidents recorded for Jungheinrich (ČR) s.r.o. in 2026.

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

Loading…

SUBSIDIARY

Jungheinrich (ČR) s.r.o. Subsidiaries

Parent Company

JS

Mechanical Or Industrial Engineering

Website: http://www.jungheinrich.cz

Company Size: 201-500 employees

No subsidiary data available for this company.

Loading…

Jungheinrich (ČR) s.r.o. Similar Companies

Loading…

NEWS

Jungheinrich (ČR) s.r.o. CyberSecurity News

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

Loading…

CVE

Latest

Global CVEs (Not Company-Specific)

CVE-2026-12484

SUMMARY

A vulnerability in keras-team/keras version 3.15.0 allows unsafe deserialization of attacker-controlled PyTorch pickle data through the public `keras.layers.TorchModuleWrapper.from_config` method. This method invokes `torch.load(..., weights_only=False)` without requiring an explicit unsafe opt-in, such as a `safe_mode=False` parameter. When called outside a `SafeModeScope(True)` context, the absence of an ambient safe mode state permits unsafe deserialization by default. This issue can lead to arbitrary code execution if untrusted Keras layer configurations are processed using this method. The vulnerability arises because the method does not enforce safe deserialization practices unless explicitly guarded by Keras safe mode.

Published

Date2026-07-19

Updated

Date2026-07-19

RISK INFORMATION (Score: 7.8)

cvss3

Base Score: 7.8

Complexity: LOW

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

Impact Score

5.9

Exploitability

1.8

REFERENCES

https://huntr.com/bounties/ab14df49-13b5-4442-b754-3189430bfa28

CVE-2026-64186

SUMMARY

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Remove latent out-of-bounds access in IOMMU debugfs In iommu_mmio_write() and iommu_capability_write(), the variables dbg_mmio_offset and dbg_cap_offset are declared as int. However, they are populated using kstrtou32_from_user(). If a user provides a sufficiently large value, it can become a negative integer. Prior to this patch, the AMD IOMMU debugfs implementation was already protected by different mechanisms. 1. #define OFS_IN_SZ 8 ensures the user string <= 8 bytes, so e.g. 0xffffffff isn't a valid input. if (cnt > OFS_IN_SZ) return -EINVAL; 2. Implicit type promotion in iommu_mmio_write(), dbg_mmio_offset is int and iommu->mmio_phys_end is u64 if (dbg_mmio_offset > iommu->mmio_phys_end - sizeof(u64)) return -EINVAL; 3. The show handlers would currently catch the negative number and refuse to perform the read. Replace kstrtou32_from_user() with kstrtos32_from_user() to parse the input, and check for negative values to explicitly prevent out-of-bounds memory accesses directly in iommu_mmio_write() and iommu_capability_write().

Published

Date2026-07-19

Updated

Date2026-07-19

RISK INFORMATION (Score: )

Impact Score

Exploitability

REFERENCES

CVE-2026-64185

SUMMARY

In the Linux kernel, the following vulnerability has been resolved: sysfs: don't remove existing directory on update failure When sysfs_update_group() is called for a named group and create_files() fails (e.g. -ENOMEM), internal_create_group() calls kernfs_remove(kn) on the group directory. In the update path, kn was obtained via kernfs_find_and_get() and refers to a directory that already existed before this call. Removing it silently destroys a sysfs group that the caller did not create. Only remove the directory if we created it ourselves. On update failure the directory remains as it is left empty by remove_files() inside create_files(), but can be repopulated by a retry.

Published

Date2026-07-19

Updated

Date2026-07-19

RISK INFORMATION (Score: )

Impact Score

Exploitability

REFERENCES

CVE-2026-64184

SUMMARY

In the Linux kernel, the following vulnerability has been resolved: mm/damon/sysfs-schemes: call missing mem_cgroup_iter_break() damon_sysfs_memcg_path_to_id() breaks mem_cgroup_iter() loop without calling mem_cgroup_iter_break(). This leaks the cgroup reference. Fix the issue by calling mem_cgroup_iter_break() before the break. The issue was discovered [1] by Sashiko.

Published

Date2026-07-19

Updated

Date2026-07-19

RISK INFORMATION (Score: )

Impact Score

Exploitability

REFERENCES

CVE-2026-64183

SUMMARY

In the Linux kernel, the following vulnerability has been resolved: efi: Allocate runtime workqueue before ACPI init Since commit 5894cf571e14 ("acpi/prmt: Use EFI runtime sandbox to invoke PRM handlers") ACPI PRM calls are delegated to a workqueue which runs in a kernel thread, making it easier to detect and mitigate faulting memory accesses performed by the firmware. Rafael reports that such PRM accesses may occur before efisubsys_init() executes, which is where the workqueue is allocated, leading to NULL pointer dereferences. Since acpi_init() [which triggers the early PRM accesses] executes as a subsys_initcall() as well, and has its own dependencies that may be sensitive to initcall ordering, deferring acpi_init() is not an option. So instead, split off the workqueue allocation into its own postcore initcall, as this is the only missing piece to allow EFI runtime calls to be made. This ensures that EFI runtime call (including PRM calls) are accessible to all code running at subsys_initcall() level.

Published

Date2026-07-19

Updated

Date2026-07-19

RISK INFORMATION (Score: )

Impact Score

Exploitability

REFERENCES

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…