Snapshot 318458
Raw (normalized text)
Scripts and page chrome removed; this is what change detection compares.
Trust & Compliance Center Start your security review View & download sensitive information Ask for information SavvyMoney is reviewed and trusted by TransUnion Amazon Overview At SavvyMoney, safeguarding your data is more than a commitment - it's an integral part of our DNA. We consider it our prime responsibility to uphold unrivaled confidentiality, privacy, and security standards to shield your data. Explore further by selecting any topic card, or enhance your access to comprehensive knowledge base responses and downloadable documentation by setting up an account. Compliance CCPA CPRA CSA STAR Level 1 CSA STAR Level 2 CSA Trusted Cloud Provider GLBA NIST CSF SOC 2 Type 2 TRUSTe Documents DOCUMENTS2024-07-31 AWS Outage RCA DOCUMENTSCertificate of Good Standing - Delaware DOCUMENTSData Security Practices DOCUMENTSLetter of Financial Standing DOCUMENTSW-9 Form REPORTS2025 Disaster Recovery Test Report REPORTSData Security Practice REPORTSPenetration Test Report COMPLIANCECSA STAR Level 1 COMPLIANCECSA STAR Level 2 COMPLIANCESOC 2 Type 2 COMPLIANCETRUSTe Risk Profile Data Access LevelRestricted Impact LevelSevere Recovery Time Objective1 hour View more Product Security Audit Logging Data Security Integrations View more Reports 2025 Disaster Recovery Test Report Data Security Practice Penetration Test Report Self-Assessments CAIQ Data Security Access Monitoring Data Backups Data Erasure View more App Security Responsible Disclosure Bot Detection Code Analysis View more Legal Subprocessors Certificate of Insurance (COI) Master Services Agreement View more Data Privacy Cookies Data Breach Notifications Data Into System View more Access Control Data Access Logging Password Security Infrastructure Status Monitoring Amazon Web Services Anti-DDoS View more Endpoint Security Disk Encryption DNS Filtering Endpoint Detection & Response View more Network Security Data Loss Prevention DNSSEC Firewall View more Corporate Security Asset Management Practices Email Protection Employee Training View more Policies Acceptable Use Policy Access Control Policy Backup Policy View more Security Grades Qualys SSL Labs SavvyMoney Platform A+ Knowledge Base (FAQ) Trust & Compliance Center Updates CSA STAR Level II Certification Achieved Compliance We proudly announce that SavvyMoney has achieved the Cloud Security Alliance (CSA) STAR Level II Certification. This prestigious certification underscores our unwavering commitment to cloud security and data protection. The CSA STAR Level II Certification is a rigorous, independent assessment that evaluates the security measures we have implemented to protect our clients' data. This certification validates our robust security framework and demonstrates our dedication to maintaining the highest cloud security standards. At SavvyMoney, we strive to give our clients the utmost confidence in our security practices. Achieving the CSA STAR Level II Certification reinforces our promise to safeguard sensitive information and deliver exceptional service. Please login to download the CSA STAR Level II Certification. OpenSSH Password Authentication Bypass (November 2026) Vulnerabilities Summary SavvyMoney's SFTP service is not affected by the OpenSSH password authentication bypass disclosed on November 5, 2026. Partners don't need to take any action for SavvyMoney file transfers. About the issue On November 5, 2026, the OpenSSH project released version 10.6p2. It fixes a password authentication bypass in the OpenSSH server (sshd). No CVE had been assigned when this notice was written. The issue only affects sshd on Linux systems built on the musl C library, such as Alpine Linux, when sshd was built without PAM. All of the following must also be true: Password authentication is enabled. An account has its password field set to exactly *, such as root or a key-only account. Another account on the system has a real password. The attacker knows the targeted account's username. When all of these are true, an attacker can log in to that account without its real password. Systems built on glibc, systems using PAM, Dropbear, and OpenBSD are not affected. See the Alpine Linux advisory for details. Our assessment We reviewed our SFTP service and the servers that run it on November 5, 2026. It is not affected for two separate reasons: Our SFTP service does not use OpenSSH. Partner file transfers go through the SSH server built into our managed file transfer platform. It is different software from OpenSSH. None of the servers in our SFTP environment use musl. They run enterprise Linux distributions built on glibc, with PAM enabled. The OpenSSH project and Alpine both list these systems as not affected. Either reason alone rules out this issue. What we're doing We are reviewing the rest of our environment for any musl-based system that runs OpenSSH. We will update this notice if that review changes our assessment. We continue to apply vendor security updates through our standard patch management process. We are monitoring vendor and industry updates, such as a CVE assignment or a change in affected systems, and will update this notice if anything changes. Do partners need to do anything? No action is needed for file transfers with SavvyMoney. Your SFTP credentials, SSH keys, and connection settings stay the same. For your own systems, check for sshd running on Alpine Linux or another musl-based system. If you find any, upgrade OpenSSH to 10.6p2 or later. If you can't upgrade right away, set PasswordAuthentication to no in the sshd configuration and restart sshd. Questions Contact your SavvyMoney Partner Success Manager, or our security team at security@savvymoney.com. SavvyMoney Security CVE-2026-111497 (Brotli decoder vulnerability, "Brotli2Shell") Vulnerabilities To our partners and customers, SavvyMoney is aware of CVE-2026-111497, also called Node2Shell, HTTP2Shell, Broccoli2Shell or Brotli2Shell. It is an out-of-bounds write in the decoder of Google's Brotli compression library, versions 1.0.3 through 1.2.0. Google rates it 9.2 (Critical) under CVSS v4.0. If exploited, it could crash an application, expose memory contents, corrupt memory, or run attacker-supplied code. The vendor released fixes on October 21, 2026. Public proof-of-concept exploits are available, and CISA added this vulnerability to its Known Exploited Vulnerabilities catalog on October 27, 2026. The flaw can affect the Brotli library directly, as well as the many runtimes, frameworks, container images, and third-party products that bundle it. This notice explains what we checked, what we found, and what we have done. It answers the questions we most often receive through third-party risk management reviews and may serve as our written confirmation for those reviews. Summary We found the vulnerable Brotli decoder in a limited number of components that support SavvyMoney services. None of our Internet-facing services decompress Brotli content sent by external users. We remediated all affected production systems by November 3, 2026: most by October 29, 2026, and the last, an internal document-rendering service, on November 3, 2026. We have found no sign that this vulnerability was successfully exploited in our environment. We have found no evidence that any partner, customer, or member data was accessed, changed, disclosed, or taken because of this vulnerability. How we assessed exposure Our assessment covered both direct and transitive (bundled) dependencies, including: Application language runtimes and their bundled libraries Container base images and the operating-system packages inside them Web frameworks and HTTP libraries used by our applications Embedded components such as document-rendering engines Third-party and cloud service providers that support our services We used automated vulnerability scanning of our container images and matched the results against the software actually running in production, rather than relying only on build or ticket records. For each affected service, we then reviewed the code and frameworks to find where Brotli data is actually decoded. We confirmed the results with controlled tests in a non-production environment. For third-party and cloud providers, we reviewed vendor advisories and requested confirmation where needed. Answers to common questions 1. Is CVE-2026-111497 applicable to systems that support SavvyMoney services or handle partner data? Yes. The vulnerable Brotli decoder was present in a limited number of components in our environment, as described below. 2. Which products or components were affected? Application runtime: certain versions of the Node.js runtime, which bundles its own copy of the Brotli decoder, are used by a limited number of our services. Other application libraries: we also checked Java (brotli4j), Python (the brotli and brotlicffi packages, and HTTP clients such as urllib3, requests, httpx, and aiohttp that decompress Brotli automatically), and Go (andybalholm/brotli), and found none of them in use in production. Operating-system library: the Brotli library is included in some of our container images and used by standard tools such as an HTTP client, a font library, and a headless browser used for document rendering. Third-party and cloud providers: AWS reported in Security Bulletin 2026-155 that its managed Lambda runtimes for Node.js and .NET were affected, and it has deployed updated runtimes. Our review of other vendor advisories found no affected components in services that support SavvyMoney. 3. Which affected versions were present? Node.js: releases earlier than the fixed versions (22.23.4, 24.22.1 and 26.12.1), including Node.js 24.14.0. Brotli library: versions 1.1.0 and 1.2.0, as packaged by the Linux distributions used in our container images. Upstream Brotli fixed the flaw in version 1.2.1, and Linux distributions also ship the fix as patches to their existing package versions. 4. Were affected components Internet-facing, or able to process Brotli-compressed data from untrusted sources? Internet-facing services: some affected services receive traffic from the Internet. Our code review and testing found that none of them decompress Brotli-encoded content sent by external users. Where these services decode Brotli, they do so only in responses from established service providers they call. Exploiting that path would require a malicious or compromised provider, and these services are now patched. Internal services: one affected service can decode Brotli content in the requests it receives. It is an internal document-rendering service that cannot be reached from the Internet and is intended to receive requests only from other SavvyMoney systems. We remediated it on November 3, 2026. Operating-system library: In our container images, we use the library only in ways that do not process data from external users, except for the internal document-rendering service described above. 5. Have you found any sign of exploitation, compromise, unauthorized access or suspicious activity? We have found no indication of successful exploitation. We searched our web application firewall logs from October 1, 2026 through November 3, 2026 for requests carrying Brotli-compressed content. We reviewed application and error logs, unexpected crashes and restarts, and alerts from our threat-detection tooling. We observed a small number of requests with Brotli-compressed content from a few sources, consistent with Internet-wide scanning for this vulnerability. None reached a SavvyMoney service that decodes Brotli request content; they were either redirected at our load balancer or rejected, and the receiving systems showed no errors, crashes, or restarts. 6. Was any partner, customer or member data accessed, changed, disclosed or taken because of this vulnerability? We have found no evidence that any partner, customer, or member data was accessed, changed, disclosed, or exfiltrated as a result of this vulnerability. 7. Has remediation been completed? Production: Yes. The team completed remediation of all affected production systems by November 3, 2026. Most were remediated by October 29, 2026; the internal document-rendering service described in question 4 was remediated on November 3, 2026. Node.js runtime upgraded to a fixed release (24.22.1 or later). Rebuilt container images with the patched Brotli library from each Linux distribution's security updates. Non-production: In progress. We will remediate a small number of development systems by 11/30/2026. Until then, the following controls are in place: These systems hold no production, partner, customer, or member data. They are not reachable from the public Internet. Access is limited to authenticated SavvyMoney personnel through single sign-on and our zero-trust network access controls. We continue to monitor them under our standard security practices. Ongoing monitoring We continue to scan our container images and running workloads for this and other vulnerabilities, and we track vendor advisories for further updates. We will update this notice if our assessment changes. Contact Questions about this notice, or requests for additional confirmation as part of a third-party risk review, can be sent to security@savvymoney.com or to your SavvyMoney account representative. SavvyMoney Information Security PHP Vulnerabilities (PHP2Shell, CVE-2026-109618 and CVE-2026-109619) Vulnerabilities Security Advisory: PHP Vulnerabilities (PHP2Shell, CVE-2026-109618 and CVE-2026-109619) Published: October 21, 2026. Last updated: October 21, 2026. Status: Monitoring Summary On October 21, 2026, the PHP project released security updates to address two critical vulnerabilities, known as "PHP2Shell" (CVE-2026-109618 and CVE-2026-109619). If left unpatched, these vulnerabilities could allow an attacker to run code on an affected web server without logging in. SavvyMoney has reviewed its environment for exposure to these vulnerabilities. Impact on the SavvyMoney Platform The SavvyMoney platform does not use PHP. That includes the credit score widget, APIs, single sign-on integrations, and the services that store or process member data. These vulnerabilities do not affect the SavvyMoney platform or the data we process on behalf of our partners. Impact on the SavvyMoney Marketing Website Our public marketing website (www.savvymoney.com) runs on WordPress and PHP. A managed hosting provider hosts it. The website contains no member or partner data and is not connected to the SavvyMoney platform. Our hosting provider has implemented protections against these vulnerabilities at its network and hosting layers and applied PHP security updates across its platform. Action Required No action is required from our partners or their members. Our Ongoing Commitment SavvyMoney monitors security advisories and assesses new vulnerabilities as part of our vulnerability management program. We will update this notice if anything changes. Contact If you have questions about this advisory, please contact your SavvyMoney relationship manager or email security@savvymoney.com. Security Update: Shai Hulud 2.0 Supply-Chain Malware Vulnerabilities Dear Partner, We want to provide clarity regarding the recently reported Shai Hulud 2.0 supply-chain malware affecting specific open-source packages. SavvyMoney has completed an internal review and has not been impacted. Validated Findings There is no evidence of impact to SavvyMoney’s codebase, infrastructure, partner integrations, or production systems. Our security team performed a full review of dependency packages, development pipelines, and build systems. No affected components were identified. As part of standard protocol, we confirmed all credentials, pipeline secrets, and access tokens remain secure and rotated as required by policy. All SavvyMoney services are operating normally, and no action is required from partners. We take supply-chain security seriously and continue to monitor this event in coordination with our security vendors and ecosystem partners. If new information emerges, we will notify you. If you have any questions, please contact SavvyMoney Security at security@savvymoney.com. Thank you, SavvyMoney Security Team