Listen to this Post
A Critical Warning for SAP Enterprise Customers
A maximum-severity vulnerability in SAP Commerce Cloud has put enterprise e-commerce environments under renewed security pressure. The newly identified flaw, tracked as CVE-2026-58231, carries the highest possible CVSS score of 10.0 and could allow an unauthenticated attacker to execute arbitrary code through the platform’s Data Hub Adapter.
For organizations that depend on SAP Commerce Cloud to power online stores, product catalogs, customer interactions, pricing systems, and integrations with broader enterprise infrastructure, this is not a vulnerability that should be left in a normal patch queue. A flaw that combines remote accessibility, insufficient authorization, weak input validation, and arbitrary code execution can potentially transform a seemingly isolated application weakness into a gateway toward much larger systems.
SAP has released fixes, while security specialists including Onapsis are urging affected organizations to apply the corrected Commerce Cloud release and redeploy the updated environment. SAP’s own documentation confirms that the Data Hub Adapter forms an important integration layer between SAP Commerce and Data Hub, with authentication and configuration controls governing communication between the systems.
CVE-2026-58231: Why a 10.0 Score Matters
The most alarming detail is the
In this case, the weakness reportedly allows an attacker who does not need to authenticate to interact with affected functionality using specially crafted input. The problem involves inadequate authorization checks and insufficient validation of data submitted to vulnerable functions.
That combination is particularly dangerous because authentication is normally one of the first defensive barriers protecting enterprise applications. If an attacker can reach a vulnerable endpoint without first proving who they are, the security burden shifts heavily toward the application itself.
The Data Hub Adapter Is More Important Than It Looks
The affected component is the Data Hub Adapter, an SAP Commerce extension designed to connect SAP Commerce with Data Hub. SAP documentation describes Data Hub and SAP Commerce as communicating through a client-server architecture, with authentication mechanisms used on both sides.
This makes the vulnerability especially interesting from an architectural perspective. Integration components are often trusted because they sit between systems that organizations already consider legitimate.
An attacker who compromises such a component may therefore gain access to functionality that was never intended to be exposed to an untrusted party.
Unauthenticated Access Raises the Stakes
The reported attack scenario begins with an unauthenticated attacker abusing a default authentication client and submitting specially crafted input to functions that do not adequately validate or authorize the request.
The consequence is potentially severe: successful exploitation could result in arbitrary code execution and compromise internal components, affecting the confidentiality, integrity, and availability of the application.
In practical terms, arbitrary code execution means the attacker could potentially make the affected server perform actions of the attacker’s choosing, subject to the privileges and isolation available in the environment.
From Web Application Vulnerability to Enterprise Risk
The biggest concern is not simply that an attacker might compromise one Commerce Cloud component.
SAP environments frequently connect commerce platforms to identity systems, databases, ERP systems, payment services, analytics platforms, supply-chain applications, APIs, cloud services, and internal infrastructure.
A successful compromise of an internet-facing integration component could therefore become the first step in a broader intrusion.
The actual impact would depend on the affected deployment, segmentation, credentials, privileges, network controls, and other security mechanisms. Nevertheless, the possibility of arbitrary code execution makes this vulnerability substantially more serious than a simple information-disclosure bug.
SAP Has Released Fixes
SAP has addressed CVE-2026-58231 through its security update process. Organizations running affected versions should move to a fixed Commerce Cloud release and then redeploy the updated environment.
That final step is important. Applying a patch to source components without completing the deployment process does not necessarily mean that the vulnerable production environment has actually been replaced.
Security teams should therefore verify the running version rather than assuming that an update process completed successfully.
Temporary Protection Through IP Filtering
For organizations that cannot immediately apply the permanent fix, Onapsis has recommended reducing exposure by configuring an IP Filter Set to restrict access to the vulnerable endpoint.
This should be treated as a temporary containment measure rather than a substitute for patching.
Network restrictions can significantly reduce an
SAP’s Existing Security Architecture Matters
SAP documentation indicates that Data Hub and the Data Hub Adapter support HTTPS and security controls intended to protect communications between the components. SAP also documents authentication requirements and configuration of credentials for Data Hub Adapter communication.
These protections remain valuable, but they illustrate an important security lesson: encryption and authentication mechanisms cannot compensate for an application-level authorization or input-validation failure.
A secure transport channel can protect traffic while the application itself still processes malicious requests incorrectly.
Three More Critical Vulnerabilities Were Patched
CVE-2026-58231 is not the only serious vulnerability addressed in SAP’s August 2026 security updates.
The update also includes three additional critical vulnerabilities affecting SAP Manufacturing Integration and Intelligence and SAP NetWeaver/ABAP environments.
Together, these issues reinforce the need for SAP administrators to evaluate the complete security update rather than focusing on a single CVE.
CVE-2026-44772 Carries a 9.9 Rating
The first additional vulnerability, CVE-2026-44772, has a reported CVSS score of 9.9 and affects SAP Manufacturing Integration and Intelligence.
The flaw involves code injection through a vulnerable servlet. According to the supplied advisory information, a low-privileged attacker could provide specially crafted input that causes the application to retrieve and process attacker-controlled content from an external source.
The resulting processing could ultimately lead to arbitrary command execution on the underlying host.
External Content Creates a Dangerous Trust Boundary
The important security concept behind CVE-2026-44772 is the application’s handling of external content.
Whenever enterprise software retrieves files, templates, stylesheets, scripts, or other resources from external locations, developers must carefully distinguish between trusted and untrusted sources.
If an attacker can influence what the server retrieves and the server subsequently processes that content with elevated privileges, a relatively simple input-manipulation vulnerability can become a path toward command execution.
SAP Introduces a Secure Transformer Control
Following the patch for CVE-2026-44772, customers are expected to maintain a new system property called Secure Transformer, containing an allowlist of hosts permitted to provide XSL files.
This is an important security control because it moves the system away from blindly trusting externally supplied resources.
Only XSL files hosted on explicitly permitted systems should be consumed by the vulnerable functionality after the required configuration is implemented.
CVE-2026-34265 Targets SAP NetWeaver and ABAP
Another critical issue, CVE-2026-34265, carries a reported CVSS score of 9.8.
The vulnerability affects Application Server ABAP for SAP NetWeaver and ABAP Platform and involves an out-of-bounds write associated with logical errors in DIAG protocol parsing.
An unauthenticated attacker could potentially exploit the flaw to trigger memory corruption.
Memory Corruption Is Never a Minor Concern
Memory corruption vulnerabilities deserve particular attention because their consequences can extend beyond application crashes.
Depending on the exact conditions and exploitability of the affected component, memory corruption can potentially expose sensitive information, terminate services, corrupt application state, or in more serious scenarios contribute to code execution.
The supplied vulnerability description specifically identifies risks involving sensitive system information disclosure and system crashes.
CVE-2026-44758 Reaches the Operating System Layer
The fourth major vulnerability is CVE-2026-44758, which has a reported CVSS score of 9.1 and affects SAP Manufacturing Integration and Intelligence.
Unlike the unauthenticated Commerce Cloud issue, this vulnerability reportedly requires a highly privileged attacker.
That distinction lowers its initial accessibility but does not eliminate its importance. If an attacker has already compromised an account with sufficient privileges, a vulnerability capable of executing arbitrary commands on the underlying operating system can become an extremely powerful escalation mechanism.
SSTI and SSRF Add Another Dimension
Onapsis reportedly linked CVE-2026-44758 to a servlet component vulnerable to server-side template injection (SSTI) and server-side request forgery (SSRF).
Those two vulnerability classes are particularly dangerous when they appear together.
SSTI can allow attacker-controlled template data to be interpreted by a server-side template engine, while SSRF can allow a server to make requests to locations that an external attacker may not be able to reach directly.
When these weaknesses are combined with inadequate isolation and excessive privileges, the resulting attack chain can become significantly more damaging.
SAP Removed the Vulnerable Servlet
The patch for CVE-2026-44758 reportedly removes the vulnerable servlet component.
Removing vulnerable functionality can sometimes be more effective than attempting to add another layer of validation around an inherently dangerous component.
It also illustrates a broader principle in enterprise security: when a feature is not essential, eliminating an attack surface can be preferable to repeatedly attempting to secure it through increasingly complicated controls.
Why SAP Vulnerabilities Deserve Immediate Attention
SAP software occupies a special position inside many organizations.
These systems often sit close to financially sensitive information, business processes, customer data, supply-chain operations, manufacturing environments, and corporate identity infrastructure.
Consequently, a vulnerability in an SAP component can have consequences that extend well beyond the software process where the flaw originally appears.
This is why critical SAP security advisories should be evaluated in the context of the organization’s entire architecture.
The Real Danger Is the Attack Chain
Attackers rarely need every vulnerability to be catastrophic by itself.
A typical enterprise intrusion can involve several stages: initial access, privilege escalation, credential theft, internal discovery, lateral movement, persistence, data collection, and finally disruption or extortion.
A critical remote code execution flaw can potentially provide the initial foothold. Other weaknesses, stolen credentials, insecure configurations, or excessive permissions can then help an attacker move deeper into the environment.
That makes patch management an important part of breaking the attack chain before it begins.
Patch Management Should Include Verification
Simply installing a security update is not enough.
Security teams should verify that the vulnerable software is actually running the fixed release, that the updated configuration is active, and that externally accessible endpoints are no longer exposing the vulnerable functionality.
Where possible, organizations should also compare deployment inventories against vulnerability-management records.
A patch that exists in a test environment but never reaches production provides no protection against a real-world attacker.
Deep Analysis: Commands for Defenders
Command 1: Identify Every Affected SAP Instance
The first priority is asset discovery.
Security teams should identify every SAP Commerce Cloud environment, Data Hub Adapter deployment, SAP Manufacturing Integration and Intelligence instance, and SAP NetWeaver/ABAP system that could fall within the affected versions.
Do not rely exclusively on manually maintained inventories.
Compare cloud deployment records, CMDB data, vulnerability scanners, SAP administration records, and network telemetry to identify forgotten or shadow environments.
Command 2: Confirm the Running Version
After identifying potentially affected systems, verify the exact running software version.
The question is not whether an administrator remembers installing a patch.
The question is whether the production instance is actually running the fixed release.
This distinction becomes particularly important in cloud and automated deployment environments where a patch may have been applied to one environment while another remains exposed.
Command 3: Patch CVE-2026-58231 First
CVE-2026-58231 should receive immediate attention because of its reported 10.0 CVSS score and unauthenticated arbitrary-code-execution potential.
Organizations should prioritize systems with internet exposure and environments supporting high-value business operations.
Command 4: Redeploy After Updating
After applying the Commerce Cloud fix, complete the required redeployment process.
Then verify that the running environment corresponds to the corrected release.
The deployment pipeline should be treated as part of the security fix rather than an administrative afterthought.
Command 5: Restrict Vulnerable Endpoints
If immediate patching is impossible, restrict access to the affected endpoint using appropriate IP filtering or equivalent network controls.
The objective is to ensure that only explicitly trusted sources can reach the service.
This should remain temporary until the permanent software fix is deployed.
Command 6: Review Authentication Configuration
Review Data Hub Adapter authentication and authorization settings.
SAP’s documentation shows that Data Hub Adapter deployments rely on configured credentials and security mechanisms for communication with Data Hub and SAP Commerce.
Administrators should confirm that default or unnecessary credentials have not been left active.
Command 7: Review Internet Exposure
Determine whether affected endpoints are accessible from the public internet.
An application that is vulnerable but isolated behind multiple security layers has a different immediate risk profile from an identical application directly exposed to untrusted traffic.
Internet exposure should therefore be treated as a major prioritization factor.
Command 8: Hunt for Suspicious Requests
Security teams should review web application logs, reverse-proxy logs, API gateways, WAF telemetry, and network monitoring data for unusual requests targeting the affected functionality.
Look for unexpected request patterns, malformed parameters, repeated probing, unusual source addresses, abnormal request volumes, and activity outside normal business workflows.
Command 9: Search for Unexpected Process Activity
Because successful exploitation could result in arbitrary code execution, defenders should examine affected systems for suspicious child processes, unexpected shell activity, unusual Java processes, unfamiliar binaries, abnormal outbound connections, and recently created files.
The goal is not simply to determine whether exploitation is possible.
The goal is to determine whether exploitation may already have happened.
Command 10: Rotate Potentially Exposed Credentials
If an affected system is suspected of compromise, credentials accessible from that environment should be reviewed.
This can include service accounts, integration credentials, API keys, database credentials, cloud tokens, and other secrets depending on the architecture.
Credential rotation should be performed carefully to avoid breaking legitimate integrations.
Command 11: Review Network Segmentation
A compromised Commerce Cloud component should not automatically provide a direct route to critical internal systems.
Organizations should review segmentation between e-commerce infrastructure, databases, ERP systems, identity services, administrative networks, and other sensitive assets.
Strong segmentation can turn a potentially devastating compromise into a contained incident.
Command 12: Validate the Secure Transformer Configuration
For organizations affected by CVE-2026-44772, the new Secure Transformer configuration deserves special attention.
Allowed hosts for XSL files should be explicitly defined and kept as narrow as operational requirements permit.
A broad allowlist can undermine the security benefit of the control.
Command 13: Remove Unnecessary Trust Relationships
Every trusted integration should have a clear business justification.
Old development servers, retired integrations, unused partner endpoints, and forgotten administrative interfaces can create unnecessary attack paths.
Security teams should take the opportunity to eliminate trust relationships that no longer serve a legitimate purpose.
Command 14: Monitor for Lateral Movement
If exploitation is suspected, monitoring should extend beyond the vulnerable SAP application.
Look for authentication attempts against internal systems, unusual administrative activity, new service accounts, unexpected database connections, suspicious file transfers, and connections to infrastructure that the application normally never contacts.
Command 15: Preserve Evidence
Do not immediately erase suspicious files or shut down every affected system without considering incident-response requirements.
Logs, process information, network connections, timestamps, authentication records, and other evidence can help determine whether exploitation occurred and how far an attacker progressed.
What Undercode Say:
The Highest-Risk Element Is the Combination
The most concerning characteristic of CVE-2026-58231 is not simply its 10.0 score.
It is the combination of unauthenticated access and arbitrary code execution.
A vulnerability requiring authentication can still be catastrophic, but an attacker first needs a valid foothold.
When authentication is removed from the equation, the exposed application itself becomes the primary barrier.
Enterprise Integrations Are Attractive Targets
Integration components deserve the same security attention as the main application.
They frequently receive data from multiple systems and may possess credentials or permissions that ordinary application users do not have.
That makes them attractive targets for attackers looking for a bridge into deeper infrastructure.
Security Boundaries Must Be Explicit
The incident also demonstrates why security boundaries cannot be based purely on assumptions.
An endpoint should never be considered safe merely because it belongs to an internal integration component.
Every endpoint should have explicit authorization, input validation, access controls, monitoring, and an appropriate trust model.
Default Behavior Is a Persistent Risk
The reported abuse of a default authentication client is another reminder that default configurations deserve scrutiny.
Default credentials, default clients, sample accounts, unnecessary endpoints, and legacy integrations are common sources of enterprise exposure.
Security teams should treat every default as something to validate rather than something to trust.
Input Validation Remains Fundamental
Modern security architecture can include zero-trust controls, endpoint detection, WAFs, behavioral analytics, and sophisticated cloud monitoring.
But none of these eliminates the importance of validating input inside the application itself.
If a vulnerable function accepts attacker-controlled data and processes it in a dangerous context, the application has already crossed a critical security boundary.
CVSS 10.0 Should Trigger Action, Not Panic
A maximum CVSS score should not automatically be interpreted as proof that every organization will suffer a breach.
CVSS describes severity and exploit characteristics, not the exact probability of compromise in every environment.
However, a 10.0 vulnerability involving unauthenticated code execution deserves urgent operational attention.
The correct response is disciplined remediation, not panic.
Patch Priority Should Follow Exposure
Internet-facing systems should normally move to the front of the patch queue.
An identical vulnerable system that is completely isolated from untrusted networks may have a different immediate risk profile.
This is why vulnerability management should combine severity with exposure, asset value, exploitability, and business impact.
Defense in Depth Still Matters
Even a perfect patching program cannot guarantee that an organization will never experience an intrusion.
Network segmentation, least privilege, strong identity controls, secure configuration, endpoint monitoring, logging, and incident-response preparation remain essential.
The objective is to ensure that one vulnerability does not become the key that unlocks the entire enterprise.
Temporary Controls Have an Expiration Date
IP filtering is useful when emergency mitigation is required.
But temporary security controls often become permanent by accident.
An organization may deploy an emergency restriction, document it as temporary, and then forget about it for months.
That creates a dangerous cycle in which the underlying vulnerability remains unresolved.
SAP Environments Need Continuous Monitoring
Large SAP environments can contain thousands of integrations and dependencies.
Security teams should therefore monitor changes continuously rather than treating SAP patching as a once-a-month administrative task.
New endpoints, new integrations, configuration changes, and newly deployed services can alter the attack surface dramatically.
Multiple Critical CVEs Increase the Operational Pressure
The August update is significant because it is not limited to one critical SAP vulnerability.
CVE-2026-44772, CVE-2026-34265, and CVE-2026-44758 add additional high-impact issues across SAP technologies.
The lesson is straightforward: administrators should review the complete security update and determine whether several separate products require remediation.
Memory Corruption Requires a Different Mindset
The NetWeaver/ABAP vulnerability demonstrates that SAP security risk is not limited to web applications.
Protocol parsers and low-level processing components can also become attack surfaces.
Memory corruption vulnerabilities can be difficult to investigate because exploitation may leave different traces depending on the attack technique.
Command Execution Changes the Game
Once arbitrary command execution becomes possible, the security conversation changes.
The attacker is no longer merely manipulating application data.
They may potentially interact with the operating system, inspect files, launch processes, establish outbound connections, or attempt to move deeper into the environment.
The exact capabilities depend on privileges and platform architecture, but the risk is fundamentally more serious.
SSTI and SSRF Should Be Treated as Chainable Weaknesses
The MII vulnerabilities are also a reminder that security weaknesses should not always be assessed independently.
SSTI, SSRF, external resource retrieval, and command execution can form a dangerous sequence.
Security reviews should therefore examine how vulnerabilities interact instead of evaluating every flaw in isolation.
The Cloud Label Does Not Eliminate Security Responsibility
Organizations sometimes assume that a cloud-hosted service automatically removes much of the security burden.
That is an unsafe assumption.
Cloud providers can secure the underlying infrastructure while customers still need to manage software versions, configurations, access policies, integrations, credentials, and application-level controls.
Attackers Look for the Weakest Door
A sophisticated enterprise may have strong endpoint protection and carefully secured identity systems.
But attackers do not need to defeat every defense.
They need to find one exposed weakness that provides a viable entry point.
That is why seemingly specialized components such as Data Hub Adapter can become strategically important.
Vulnerability Management Must Become Risk Management
The objective should not simply be to reduce the number of open CVEs.
Security teams should understand which vulnerabilities expose critical assets, which systems are internet-facing, which applications hold privileged credentials, and which weaknesses could enable lateral movement.
CVE-2026-58231 is a strong example of why context matters.
Incident Response Should Begin Before Exploitation
Organizations should prepare detection and response procedures while applying the patch.
If suspicious activity is discovered later, teams should already know which logs to inspect, which systems are connected, which credentials need rotation, and how the affected application can be isolated.
Preparation reduces response time.
Patch Verification Is as Important as Patch Installation
A completed change ticket does not equal a secure system.
Security teams should verify the actual production state.
That means checking versions, deployment status, exposed endpoints, configurations, and monitoring results.
SAP Administrators Should Work With Security Teams
Application administrators understand the SAP architecture.
Security teams understand detection, segmentation, threat hunting, and incident response.
Neither side should operate independently during a critical vulnerability response.
The fastest and safest remediation usually comes from combining both perspectives.
The Bigger Lesson Is Architectural
CVE-2026-58231 is more than another number in a vulnerability database.
It highlights how a flaw in an integration component can potentially threaten a much larger business environment.
The more interconnected an enterprise becomes, the more important it is to understand exactly where trust begins and ends.
A Patch Is Only the Beginning
Applying the SAP update should be the immediate priority, but it should not be the final security action.
Organizations should follow the patch with configuration review, endpoint verification, log analysis, credential assessment, segmentation checks, and threat hunting.
That process transforms a reactive patch into a broader security improvement.
✅ CVE-2026-58231 Is Reported as a Critical SAP Commerce Cloud Vulnerability
The supplied details identify CVE-2026-58231 as affecting the SAP Commerce Cloud Data Hub Adapter and carrying a CVSS score of 10.0. Current online reporting also describes it as an unauthenticated critical vulnerability capable of arbitrary code execution.
✅ SAP Commerce Data Hub Adapter Is a Real Integration Component
SAP’s official documentation confirms that Data Hub Adapter is an SAP Commerce extension connecting SAP Commerce with Data Hub and documents authentication mechanisms between the systems.
⚠️ Exploitation Should Not Be Confused With Confirmed Active Attacks
The severity and potential impact of CVE-2026-58231 are serious, but the available material does not establish that every vulnerable SAP Commerce Cloud environment has been exploited. Organizations should therefore treat the flaw as an urgent exposure requiring remediation rather than assuming a breach has already occurred.
Prediction
(+1) SAP Customers Will Accelerate Emergency Patching
Organizations running affected SAP Commerce Cloud environments are likely to prioritize this vulnerability ahead of lower-severity vulnerabilities because a reported CVSS 10.0 unauthenticated code-execution flaw is difficult to justify leaving exposed.
(+1) Network Restrictions Will Become a Common Short-Term Defense
Where immediate deployment is difficult, enterprises will likely tighten IP-based access controls around vulnerable Data Hub Adapter endpoints while engineering teams complete the permanent update.
(+1) SAP Security Monitoring Will Become More Aggressive
Security teams are likely to increase monitoring around SAP application endpoints, integration components, authentication activity, and unusual server-side processes as they assess whether vulnerable systems were targeted.
(-1) Unpatched Internet-Facing Systems Could Become High-Value Targets
If exploitation techniques become widely available, organizations that postpone remediation could face increasing pressure from attackers scanning for exposed SAP infrastructure.
(-1) Temporary Mitigations Could Create False Confidence
IP filtering and other compensating controls can reduce exposure, but organizations that treat them as permanent solutions could remain vulnerable if the underlying software flaw is not fixed.
(+1) The Incident Will Reinforce Secure-by-Default Principles
The combination of authorization weaknesses, input validation problems, default authentication behavior, and externally retrieved content will likely encourage SAP administrators to reassess default configurations and integration trust relationships.
(+1) Patch Verification Will Become More Important
As enterprise environments increasingly rely on automated cloud deployments, organizations will place greater emphasis on proving that the fixed version is actually running in production rather than simply confirming that a patch was downloaded or installed.
(-1) Attack Chains Could Become More Sophisticated
If attackers obtain reliable access through critical SAP weaknesses, they may attempt to combine initial compromise with credential theft, privilege escalation, lateral movement, and data theft.
(+1) Segmentation Can Limit the Damage
Organizations that isolate commerce platforms from core ERP, identity, database, and administrative networks will be better positioned to contain a compromise if exploitation occurs.
(+1) Security Teams Will Treat Integration Components as First-Class Attack Surfaces
The most important long-term lesson may be that middleware and integration services deserve the same security scrutiny as the primary business application.
Final Assessment
CVE-2026-58231 should be treated as an urgent patching priority for organizations operating affected SAP Commerce Cloud deployments. The reported combination of unauthenticated access and arbitrary code execution makes the vulnerability particularly dangerous, while the additional critical SAP vulnerabilities addressed in the same update increase the importance of reviewing the complete security release.
SAP’s own documentation demonstrates how deeply Data Hub Adapter can participate in enterprise data flows and how authentication and security controls are integrated into the architecture.
For defenders, the message is simple: identify the affected systems, restrict exposure, apply the fixed releases, redeploy, verify the production state, and investigate for suspicious activity.
The most dangerous vulnerability is not necessarily the one that exists in a security report.
It is the one that remains exposed after the security team already knows about it.
▶️ Related Video (76% Match):
🕵️📝Let’s dive deep and fact‑check.
🎓 Live Courses & Certifications:
Join Undercode Academy for Verified Certifications
🚀 Request a Custom Project:
Secure, high-velocity infrastructure and disruptive technological engineering. Contact our engineering team for high-tier development and proprietary systems:
[email protected]
💎 Smart Architecture | 🛡️ Secure by Design | ⭐ Trusted by Thousands
References:
Reported By: thehackernews.com
Extra Source Hub (Possible Sources for article):
https://www.instagram.com
Wikipedia
OpenAi & Undercode AI
Image Source:
Unsplash
Undercode AI DI v2
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow UndercodeNews & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon | 📺Youtube
