What is the official website of Orthanc Team ?

The official website of Orthanc Team is https://www.orthanc.team.

What is Orthanc Team's cybersecurity risk score?

Orthanc Team has an AI-generated cybersecurity risk score of 790 out of 1000, indicating a Fair security posture according to Rankiteo's assessment.

How many security incidents has Orthanc Team experienced?

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

Has Orthanc Team been affected by any supply chain cyber incidents ?

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

Does Orthanc Team have SOC 2 Type 1 certification ?

According to Rankiteo, Orthanc Team is not certified under SOC 2 Type 1.

Does Orthanc Team have SOC 2 Type 2 certification ?

According to Rankiteo, Orthanc Team does not hold a SOC 2 Type 2 certification.

Does Orthanc Team comply with GDPR ?

According to Rankiteo, Orthanc Team is not listed as GDPR compliant.

Does Orthanc Team have PCI DSS certification ?

According to Rankiteo, Orthanc Team does not currently maintain PCI DSS compliance.

Does Orthanc Team comply with HIPAA ?

According to Rankiteo, Orthanc Team is not compliant with HIPAA regulations.

Does Orthanc Team have ISO 27001 certification ?

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

Which industry does Orthanc Team operate in ?

Orthanc Team operates primarily in the IT System Custom Software Development industry.

How many employees does Orthanc Team have ?

Orthanc Team employs approximately 3 people worldwide.

Does Orthanc Team own any subsidiaries ?

Orthanc Team presently has no subsidiaries across any sectors.

How many LinkedIn followers does Orthanc Team have ?

Orthanc Team's official LinkedIn profile has approximately followers.

What is the NAICS classification code for Orthanc Team ?

Orthanc Team is classified under the NAICS code 541511, which corresponds to Custom Computer Programming Services.

Does Orthanc Team have a Crunchbase profile ?

No, Orthanc Team does not have a profile on Crunchbase.

Does Orthanc Team have a LinkedIn profile ?

Yes, Orthanc Team maintains an official LinkedIn profile, which is actively utilized for branding and talent engagement, which can be accessed here: https://www.linkedin.com/company/orthanc-team.

How many cybersecurity incidents has Orthanc Team experienced ?

As of September 17, 2026, Rankiteo reports that Orthanc Team has experienced 1 cybersecurity incidents.

How many peer or competitor companies does Orthanc Team have ?

Orthanc Team has an estimated 336 peer or competitor companies worldwide.

What types of cybersecurity incidents has Orthanc Team faced ?

Incident Types: The types of cybersecurity incidents that have occurred include Vulnerability.

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.

Orthanc Team

Boost Score +25 with badge (5 left)

790

/1000

Fair

815

/1000

Good

Orthanc Team Vendor Cyber Rating & Cyber Score

orthanc.team

Add Your Compliance Badge

Driven by the customer's satisfaction, Orthanc Team brings solutions to improve your radiology workflow! We have a strong technical background in Orthanc and more generally in medical imaging workflows (DICOM, HL7,...). Given the combination of our skills, we can propose a very large range of services, from the deployment of Orthanc as a mini-PACS to the development of C++ plugins by way of various Python or lua scripts...

Orthanc Team

Orthanc Team CyberSecurity News & History

Past Incidents

Attack Types

Entity

Type

Severity

Impact

Seen

Blog Details

Supply Chain Source

Incident Details

View

Orthanc Team

Vulnerability

100

1/2026

ORT1789129963

Loading…

A.I.

Orthanc Team 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 Orthanc Team

Incidents vs IT System Custom Software Development Industry Avg (This Year)

Orthanc Team has 0.0% fewer incidents than the average of same-industry companies with at least one recorded incident.

Incidents vs All-Companies Average (This Year)

Orthanc Team has 2.91% fewer incidents than the average of all companies with at least one recorded incident.

Incident Types Orthanc Team vs IT System Custom Software Development Industry Avg (This Year)

Orthanc Team reported 1 incidents this year: 0 cyber attacks, 0 ransomware, 1 vulnerabilities, 0 data breaches, compared to industry peers with at least 1 incident.

Incident History - Orthanc Team (X = Date, Y = Severity)

Loading…

SUBSIDIARY

Orthanc Team Subsidiaries

Parent Company

Orthanc Team

IT System Custom Software Development

Website: https://www.orthanc.team

Company Size: 2-10 employees

No subsidiary data available for this company.

Loading…

Orthanc Team Similar Companies

Loading…

NEWS

Orthanc Team CyberSecurity News

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

Loading…

CVE

Latest

Global CVEs (Not Company-Specific)

CVE-2026-65388

SUMMARY

A remote attacker who controls a container registry may be able to direct a client's token request to a host of the attacker's choice, and disclose the victim's registry credentials to that host. This vulnerability is addressed in containerization version 0.41.0.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: )

Impact Score

Exploitability

REFERENCES

https://github.com/apple/containerization/security/advisories/GHSA-mx96-5vvg-x2mg

CVE-2026-61599

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, the djust live transport resolves the LiveView to mount from a client-supplied dotted path by calling `__import__(module_path, ...)`. The module is imported — running its top-level code (import side effects) — before the framework checks that the resolved object is a `LiveView` subclass and before any per-view authentication. The `LIVEVIEW_ALLOWED_MODULES` allowlist that should contain this is fail-open (`if allowed_modules:` — skipped when the setting is unset, the framework default) and uses loose `startswith` matching. An unauthenticated WebSocket client (the WS handshake does not require auth; per-view auth runs only after import + instantiate) can therefore send a `mount` / `live_redirect_mount` / `url_change` frame (or an SSE mount) with `view = "<any.importable.module>.AnyName"` and cause the server to import — and execute the top-level code of — any importable Python module by name. Version 1.0.7 fixes the issue with a fail-closed resolution gate (`djust._view_resolution.is_view_import_allowed`): a client view path resolves only if (a) its module is already loaded (`sys.modules` — so resolving runs no new code; URL-routed views loaded by URLconf at startup keep working with zero config) or (b) it matches `LIVEVIEW_ALLOWED_MODULES` on a module-segment boundary (explicit opt-in for lazily-imported views). The gate runs before `__import__` at all three sinks (+ defense-in-depth inside `_instantiate_view`). As a workaround, set `LIVEVIEW_ALLOWED_MODULES` to the narrow list of modules that contain your mountable LiveView classes. (Note: pre-patch the allowlist is `startswith`-matched and the import still precedes the subclass check, so this is mitigation, not a complete fix.)

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: )

cvss4

Base Score: 8.8

Complexity: LOW

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:H/VA:L/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

CVE-2026-61596

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, djust's per-object authorization (`get_object` + `has_object_permission`, ADR-017) was enforced on the WebSocket mount and event paths but not on three other render entry points: (a) the initial HTTP GET render, (b) SPA `url_change` navigation, and (c) `{% live_render %}` embedded child views. An authenticated user could therefore view (and on some paths act on) an object they are not authorized for by loading the page directly, navigating to it via SPA url-change, or composing it as an embedded child — a classic IDOR / broken object-level access control on object-scoped views. This is fixed in djust 1.0.7. All render entry points now route through a shared `enforce_object_permission` chokepoint: HTTP GET returns 403, `url_change` emits a `permission_denied` frame and skips the render, and `{% live_render %}` (eager + lazy) refuses the embed. Views without a custom `get_object` are unaffected (no-op). No reliable workaround short of upgrading. Do not expose object-scoped views through the HTTP-GET / url_change / live_render paths until patched.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: 7.1)

cvss3

Base Score: 7.1

Complexity: LOW

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

Impact Score

4.2

Exploitability

2.8

REFERENCES

CVE-2026-61589

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, the WebSocket `handle_mount` and `ViewRuntime._build_request` rebuild an `HttpRequest` via `RequestFactory().get(...)` with no `HTTP_HOST`, so `request.get_host()` defaulted to `"testserver"` on the live path. Host/subdomain/domain `TenantResolver`s then misresolved the tenant — `None` on the live path while the HTTP path resolved correctly. With `STRICT_MODE=False` the tenant-scoped managers returned unscoped rows (cross-tenant disclosure); with the default they returned an empty queryset (broken tenancy). This is fixed in djust 1.0.7. The handshake Host is extracted from the ASGI scope, validated against `ALLOWED_HOSTS` (the same logic as the CSWSH Origin gate, parsed with Django's `split_domain_port` so malformed Hosts are rejected at the boundary), and propagated — with the TLS scheme — into the reconstructed request, so live-path tenant resolution matches HTTP exactly. There is no known workaround on the live path short of upgrading. Users are most exposed when combined with `STRICT_MODE=False`.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: 6.3)

cvss3

Base Score: 6.3

Complexity: HIGH

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

Impact Score

Exploitability

1.8

REFERENCES

CVE-2026-61588

SUMMARY

djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance. Prior to version 1.0.7, when a Django `Model` instance is assigned to a public view attribute, djust serialized it to the client with no sensitive-field denylist — sending fields such as `password` (the hash), privilege flags (e.g. `is_staff` / `is_superuser`), tokens, and other PII to the browser. Because exposing model objects to templates is a normal djust pattern, this could leak credentials/PII without the developer realizing the full object crossed the wire. This is fixed in djust 1.0.7. Model serialization applies a secure-by-default sensitive-field denylist (password/hash/token/secret-style fields and known privilege flags are withheld) with an identity-subset fallback. As a workaround, keep `Model` instances on `_private` attributes and expose only the specific fields needed, until patched.

Published

Date2026-09-16

Updated

Date2026-09-16

RISK INFORMATION (Score: 6.5)

cvss3

Base Score: 6.5

Complexity: LOW

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

Impact Score

3.6

Exploitability

2.8

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…

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

Trusted by insurers. Chosen by leaders.

Orthanc Team Vendor Cyber Rating & Cyber Score

Orthanc Team A.I CyberSecurity Scoring

Orthanc Team CyberSecurity News & History

Orthanc Team Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Incident Predictions locked

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

A.I. Risk Score Predictions locked

Underwriter Stats for Orthanc Team

Incidents vs IT System Custom Software Development Industry Avg (This Year)

Incidents vs All-Companies Average (This Year)

Incident Types Orthanc Team vs IT System Custom Software Development Industry Avg (This Year)

Incident History - Orthanc Team (X = Date, Y = Severity)

Orthanc Team Subsidiaries

Parent Company

Orthanc Team

Orthanc Team Similar Companies

Orthanc Team CyberSecurity News

Global CVEs (Not Company-Specific)

Access Data Using Our API

What Do We Measure ?

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

Rankiteo

Orthanc Team CyberSecurity News & History

Orthanc Team Company Scoring based on AI Models

Cyber Incidents Likelihood 3 - 6 - 9 months

Incident Predictions locked

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

A.I. Risk Score Predictions locked

Underwriter Stats for Orthanc Team

Incidents vs IT System Custom Software Development Industry Avg (This Year)

Incidents vs All-Companies Average (This Year)

Incident Types Orthanc Team vs IT System Custom Software Development Industry Avg (This Year)

Incident History - Orthanc Team (X = Date, Y = Severity)

Orthanc Team Subsidiaries

Parent Company

Orthanc Team

Orthanc Team Similar Companies

Orthanc Team CyberSecurity News

Global CVEs (Not Company-Specific)

Access Data Using Our API

What Do We Measure ?

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

Rankiteo