Vulnerability Scan Result

Target:

http://remo.health/ (redirect)

Scanned target: https://remo.health/

Submitted: May 02, 2026 from GD

Public Scan

Scan mode: Passive (non-intrusive)

Summary

medium

Info

Low

Medium

High

Critical

Screenshot

Title:	Better dementia care - Remo Health
Description:	Remo Health is a virtual dementia care company. Get expert guidance, caregiver support, and clinical care.

IP Information

ip_address	172.66.40.241
country	-
network_name	Cloudflare, Inc.
asn	AS13335

ip_address	172.66.43.15
country	-
network_name	Cloudflare, Inc.
asn	AS13335

Open Ports

80/tcp	http	Cloudflare http proxy -
443/tcp	https	cloudflare -
2082/tcp	http	Cloudflare http proxy -
2083/tcp	https	nginx -
2086/tcp	http	Cloudflare http proxy -
2087/tcp	https	nginx -
8080/tcp	http	Cloudflare http proxy -
8443/tcp	https-alt	cloudflare -

Web Technologies

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
Google Cloud	IaaS
Google Cloud CDN	CDN
Google Sign-in	Authentication
HTTP/3	Miscellaneous
LaunchDarkly	Feature management
Next.js 14.2.35	JavaScript frameworks, Web frameworks, Web servers, Static site generator
PHP	Programming languages
React	JavaScript frameworks
Segment	Customer data platform
PWA	Miscellaneous
Webpack	Miscellaneous
Priority Hints	Performance
Cloudflare	CDN
Cloudflare Bot Management	Security
Datadog	RUM, Analytics
HSTS	Security

Web Application Vulnerabilities

Evidence

CVE	CVSS	EPSS Score	EPSS Percentile	Summary
CVE-2026-27980	6.9	0.00022	0.06218	Next.js is a React framework for building full-stack web applications. Starting in version 10.0.0 and prior to version 16.1.7, the default Next.js image optimization disk cache (`/_next/image`) did not have a configurable upper bound, allowing unbounded cache growth. An attacker could generate many unique image-optimization variants and exhaust disk space, causing denial of service. This is fixed in version 16.1.7 by adding an LRU-backed disk cache with `images.maximumDiskCacheSize`, including eviction of least-recently-used entries when the limit is exceeded. Setting `maximumDiskCacheSize: 0` disables disk caching. If upgrading is not immediately possible, periodically clean `.next/cache/images` and/or reduce variant cardinality (e.g., tighten values for `images.localPatterns`, `images.remotePatterns`, and `images.qualities`).
CVE-2026-29057	6.3	0.00031	0.08954	Next.js is a React framework for building full-stack web applications. Starting in version 9.5.0 and prior to versions 15.5.13 and 16.1.7, when Next.js rewrites proxy traffic to an external backend, a crafted `DELETE`/`OPTIONS` request using `Transfer-Encoding: chunked` could trigger request boundary disagreement between the proxy and backend. This could allow request smuggling through rewritten routes. An attacker could smuggle a second request to unintended backend routes (for example, internal/admin endpoints), bypassing assumptions that only the configured rewrite destination/path is reachable. This does not impact applications hosted on providers that handle rewrites at the CDN level, such as Vercel. The vulnerability originated in an upstream library vendored by Next.js. It is fixed in Next.js 15.5.13 and 16.1.7 by updating that dependency’s behavior so `content-length: 0` is added only when both `content-length` and `transfer-encoding` are absent, and `transfer-encoding` is no longer removed in that code path. If upgrading is not immediately possible, block chunked `DELETE`/`OPTIONS` requests on rewritten routes at the edge/proxy, and/or enforce authentication/authorization on backend routes.
CVE-2025-59471	5.9	0.00027	0.07641	A denial of service vulnerability exists in self-hosted Next.js applications that have `remotePatterns` configured for the Image Optimizer. The image optimization endpoint (`/_next/image`) loads external images entirely into memory without enforcing a maximum size limit, allowing an attacker to cause out-of-memory conditions by requesting optimization of arbitrarily large images. This vulnerability requires that `remotePatterns` is configured to allow image optimization from external domains and that the attacker can serve or control a large image on an allowed domain. Strongly consider upgrading to 15.5.10 or 16.1.5 to reduce risk and prevent availability issues in Next applications.

Vulnerability description

Outdated or vulnerable software components include versions of server-side software that are no longer supported or have known, publicly disclosed vulnerabilities. Using outdated software significantly increases the attack surface of a system and may allow unauthorized access, data leaks, or service disruptions. Vulnerabilities in these components are often well-documented and actively exploited by attackers. Without security patches or vendor support, any weaknesses remain unmitigated, exposing the application to risks. In some cases, even after patching, the reported version may remain unchanged, requiring manual verification.

Risk description

The risk is that an attacker could search for an appropriate exploit (or create one himself) for any of these vulnerabilities and use it to attack the system. Since the vulnerabilities were discovered using only version-based testing, the risk level for this finding will not exceed 'high' severity. Critical risks will be assigned to vulnerabilities identified through accurate active testing methods.

Recommendation

In order to eliminate the risk of these vulnerabilities, we recommend you check the installed software version and upgrade to the latest version.

Classification

CWE	CWE-1035
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL Evidence

URL	Evidence
https://remo.health/	Response headers include the HTTP Content-Security-Policy security header with the following security issues:`script-src-elem: Nonces should only use the base64 charset. script-src: Nonces should only use the base64 charset. connect-src: Nonces should only use the base64 charset. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. style-src: Nonces should only use the base64 charset.`

https://remo.health/

Response headers include the HTTP Content-Security-Policy security header with the following security issues:script-src-elem: Nonces should only use the base64 charset. script-src: Nonces should only use the base64 charset. connect-src: Nonces should only use the base64 charset. script-src: 'self' can be problematic if you host JSONP, Angular or user uploaded files. style-src: Nonces should only use the base64 charset.

Vulnerability description

We noticed that the Content-Security-Policy (CSP) header configured for the web application includes unsafe directives. The CSP header activates a protection mechanism implemented in web browsers which prevents exploitation of Cross-Site Scripting vulnerabilities (XSS) by restricting the sources from which content can be loaded or executed.

Risk description

For example, if the unsafe-inline directive is present in the CSP header, the execution of inline scripts and event handlers is allowed. This can be exploited by an attacker to execute arbitrary JavaScript code in the context of the vulnerable application.

Recommendation

Remove the unsafe values from the directives, adopt nonces or hashes for safer inclusion of inline scripts if they are needed, and explicitly define the sources from which scripts, styles, images or other resources can be loaded.

Classification

CWE	CWE-1021
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

Software / Version	Category
Amazon Web Services	PaaS
Amazon S3	CDN
Google Cloud	IaaS
Google Cloud CDN	CDN
Google Sign-in	Authentication
HTTP/3	Miscellaneous
LaunchDarkly	Feature management
Next.js 14.2.35	JavaScript frameworks, Web frameworks, Web servers, Static site generator
PHP	Programming languages
React	JavaScript frameworks
Segment	Customer data platform
PWA	Miscellaneous
Webpack	Miscellaneous
Priority Hints	Performance
Cloudflare	CDN
Cloudflare Bot Management	Security
Datadog	RUM, Analytics
HSTS	Security

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Classification

CWE	CWE-200
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Evidence

URL
https://remo.health/robots.txt

Vulnerability description

We found the robots.txt on the target server. This file instructs web crawlers what URLs and endpoints of the web application they can visit and crawl. Website administrators often misuse this file while attempting to hide some web pages from the users.

Risk description

There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be considered a security measure, as this file can be directly accessed and read by anyone.

Recommendation

We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website (ex. administration panels, configuration files, etc).

Evidence

URL
Missing: https://remo.health/.well-known/security.txt

Vulnerability description

We have noticed that the server is missing the security.txt file, which is considered a good practice for web security. It provides a standardized way for security researchers and the public to report security vulnerabilities or concerns by outlining the preferred method of contact and reporting procedures.

Risk description

There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated channel for reporting vulnerabilities and security issues.

Recommendation

We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security issues they find, improving the defensive mechanisms of your server.

Classification

CWE	CWE-1188
OWASP Top 10 - 2017
OWASP Top 10 - 2021

Infrastructure Vulnerabilities

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.remo.health	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:f48443e74f41480cabfe1b993779c223@dmarc-reports.cloudflare.net,mailto:dmarc_agg@vali.email"

Vulnerability description

We found that the DMARC record for the domain is not configured with ruf tag. A missing ruf (forensic reporting) tag in a DMARC record indicates that the domain owner has not enabled the collection of detailed failure reports. Forensic reports provide valuable insights into specific instances where emails fail DMARC authentication. Without the ruf tag, the domain administrator loses the ability to receive and analyze these reports, making it difficult to investigate individual email failures or identify targeted phishing or spoofing attacks that may be exploiting weaknesses in the email authentication setup.

Risk description

Without forensic reports (ruf), domain owners have limited visibility into the specifics of failed DMARC validation. This means potential malicious activity, such as email spoofing or phishing attempts, might go unnoticed until they result in more significant security breaches or reputational damage. Forensic reports allow for quick response to email abuses by providing detailed information about the failure, including the header information of the emails involved. The absence of this data hampers an organization's ability to identify and mitigate threats targeting its domain, increasing the risk of ongoing spoofing and fraud.

Recommendation

We recommend configuring the ruf tag in the DMARC record. This tag specifies where forensic reports should be sent, providing the domain owner with detailed data on DMARC validation failures. Forensic reports allow administrators to analyze why certain emails failed authentication, making it easier to fine-tune DMARC policies or address potential vulnerabilities. Ensure that the ruf email address belongs to a secure and trusted location capable of handling sensitive email data.

Evidence

Domain Queried	DNS Record Type	Description	Value
_dmarc.remo.health	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:f48443e74f41480cabfe1b993779c223@dmarc-reports.cloudflare.net,mailto:dmarc_agg@vali.email"

Vulnerability description

We found that the DMARC record for the domain is not configured with sp policy, meaning that no policy is enforced for subdomains. When a DMARC record does not include a subdomain policy (sp directive), subdomains are not explicitly covered by the main domain's DMARC policy. This means that emails sent from subdomains (e.g., sub.example.com) may not be subject to the same DMARC enforcement as the main domain (example.com). As a result, attackers could potentially spoof emails from subdomains without being blocked or flagged, even if the main domain has a strict DMARC policy.

Risk description

Without a subdomain policy (sp directive) in the DMARC record, subdomains are not protected by the same DMARC enforcement as the main domain, leaving them vulnerable to spoofing attacks. This inconsistency can be exploited by attackers to send phishing emails from subdomains, undermining the organization’s overall email security.

Recommendation

To mitigate the risk, we recommend configuring the DMARC record with a subdomain policy by adding the sp=reject or sp=quarantine directive. This will extend DMARC enforcement to all subdomains, preventing spoofing attempts and maintaining consistent security across both the main domain and its subdomains.

Operating System	Accuracy
FreeBSD 11.0-RELEASE	91%

Evidence

Software / Version	Category
Cloudflare	CDN

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Domain Queried	DNS Record Type	Description	Value
remo.health	A	IPv4 address	172.66.40.241
remo.health	A	IPv4 address	172.66.43.15
remo.health	NS	Name server	jimmy.ns.cloudflare.com
remo.health	NS	Name server	marissa.ns.cloudflare.com
remo.health	MX	Mail server	1 aspmx.l.google.com
remo.health	MX	Mail server	5 alt1.aspmx.l.google.com
remo.health	MX	Mail server	5 alt2.aspmx.l.google.com
remo.health	MX	Mail server	10 aspmx2.googlemail.com
remo.health	MX	Mail server	10 aspmx3.googlemail.com
remo.health	SOA	Start of Authority	jimmy.ns.cloudflare.com. dns.cloudflare.com. 2403133627 10000 2400 604800 1800
remo.health	AAAA	IPv6 address	2606:4700:3108::ac42:28f1
remo.health	AAAA	IPv6 address	2606:4700:3108::ac42:2b0f
remo.health	TXT	Text record	"MS=ms79184366"
remo.health	TXT	Text record	"linear-domain-verification=n3xtcci8ntda"
remo.health	TXT	Text record	"apple-domain-verification=tpHTiiJLKAUftvIC"
remo.health	TXT	Text record	"docusign=fef8ff2c-dead-4a0c-87d3-632af696f518"
remo.health	TXT	Text record	"1password-site-verification=EAEOPYMZ3BBUFOB54FGBFOFZJI"
remo.health	TXT	Text record	"miro-verification=4f967c5099a5cf2523d094211fcf505bd6459f11"
remo.health	TXT	Text record	"segment-site-verification=ejz1256IjY14j7aAWwL1xVchJctMI4Ss"
remo.health	TXT	Text record	"facebook-domain-verification=vfw1ka0vxr8q3h3o37pok8jowv70xj"
remo.health	TXT	Text record	"mixpanel-domain-verify=f7af63af-cb5e-46fa-a48d-a11a033cdfab"
remo.health	TXT	Text record	"twilio-domain-verification=1391b9bd78794fbdcf0f1648b28f68b5"
remo.health	TXT	Text record	"anthropic-domain-verification-0xhgw7=EuEZfHRvL203cJ1CxeB1mUrYN"
remo.health	TXT	Text record	"slack-domain-verification=UCKZkLrNxgvcSffneqNvsAx8N3BEzlaaUnvZkMXI"
remo.health	TXT	Text record	"google-site-verification=G0boFGHj5lodTzBOVGZHJXmih7lCf92IKwX8D6M5cUE"
remo.health	TXT	Text record	"google-site-verification=MGtOVhJCKwHXfpIWKzBu3kChl4J70TaQVrLbZV0-yLg"
remo.health	TXT	Text record	"google-site-verification=YmuLKUSQKINw-Bh55_ChbbwB0w7HrHH4oYjyWHu_5Kw"
remo.health	TXT	Text record	"google-site-verification=nIYdWR-nS_TlD-TtaehZsGcR3Tiy76xfJ9tUt7jJYOA"
remo.health	TXT	Text record	"google-site-verification=xi7_3MBfPS5tiBPSE04LfkacguxwpKvaZHXhd67GORs"
remo.health	TXT	Text record	"notion-domain-verification=R6z9e9PWZ9Ewgez1IXBVjuxesshDnZesErgGOpcow4r"
remo.health	TXT	Text record	"stripe-verification=1F9970B388A8E1CF9A8C975E7F2113E89F4CB79E4EB52F686E1D2B144FF3B771"
remo.health	TXT	Text record	"hcp-domain-verification=f62dfdc07b0721bf456db69ea20f8049fbcda999c1d655259a2494e3460e6eb0"
remo.health	TXT	Text record	"figma-domain-verification=16491209eecb47f243791b612d5f1a05a7ed7dc27c4799220cdce65c1c0a99c2-1740007877"
remo.health	SPF	Sender Policy Framework	"v=spf1 include:_spfcf1.remo.health include:_spfcf2.remo.health include:_spfcf3.remo.health include:_spf.google.com include:spf.protection.outlook.com include:_spf.paubox.com -all"
remo.health	CAA	Certificate Authority Authorization	0 issue "amazon.com"
remo.health	CAA	Certificate Authority Authorization	0 issue "amazonaws.com"
remo.health	CAA	Certificate Authority Authorization	0 issue "amazontrust.com"
remo.health	CAA	Certificate Authority Authorization	0 issue "awstrust.com"
remo.health	CAA	Certificate Authority Authorization	0 issue "comodoca.com"
remo.health	CAA	Certificate Authority Authorization	0 issue "digicert.com; cansignhttpexchanges=yes"
remo.health	CAA	Certificate Authority Authorization	0 issue "letsencrypt.org"
remo.health	CAA	Certificate Authority Authorization	0 issue "pki.goog; cansignhttpexchanges=yes"
remo.health	CAA	Certificate Authority Authorization	0 issue "ssl.com"
remo.health	CAA	Certificate Authority Authorization	0 issuewild "comodoca.com"
remo.health	CAA	Certificate Authority Authorization	0 issuewild "digicert.com; cansignhttpexchanges=yes"
remo.health	CAA	Certificate Authority Authorization	0 issuewild "letsencrypt.org"
remo.health	CAA	Certificate Authority Authorization	0 issuewild "pki.goog; cansignhttpexchanges=yes"
remo.health	CAA	Certificate Authority Authorization	0 issuewild "ssl.com"
_dmarc.remo.health	TXT	Text record	"v=DMARC1; p=reject; rua=mailto:f48443e74f41480cabfe1b993779c223@dmarc-reports.cloudflare.net,mailto:dmarc_agg@vali.email"

Risk description

An initial step for an attacker aiming to learn about an organization involves conducting searches on its domain names to uncover DNS records associated with the organization. This strategy aims to amass comprehensive insights into the target domain, enabling the attacker to outline the organization's external digital landscape. This gathered intelligence may subsequently serve as a foundation for launching attacks, including those based on social engineering techniques. DNS records pointing to services or servers that are no longer in use can provide an attacker with an easy entry point into the network.

Recommendation

We recommend reviewing all DNS records associated with the domain and identifying and removing unused or obsolete records.

Evidence

Software / Version	Category
Cloudflare	CDN

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

DKIM selector	Key type	Key size	Value
google	rsa	1422	"v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAhHuxc61cVlEY83iOOMQyygE4OaBHlu2vPqZQvPxP/xUNgGIE9/5Qg+fbse8SM9YCWyEs2egWo056CxgRyPieb1t08kRXcOdkpGRPJqmV1DLF0rGUX8sfhI2pgV9n6cd5ClRXHcqYTFlOtclWa4BVifbQ/9HrvQxVZY0J5wGbFAIIBm/sloTTzlCbyDvqD5N6D" "1ZVDFV7WbDAHvOtx7yYMdzYiVgspTlMgeiLZooxLJTUVG/aniz8RldrAiPr0u7CBRy0dy84fPP/fBrZG4ppJRqY6DE8JfnTMGJ6YmuOJ7hCekdAIXIDbu+FRH7lJsqauYTc/bIrSuAxZH1LFgCi6QIDAQAB"
s2	rsa	1296	"k=rsa; t=s; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC5rLHKHXu4DB3GMuadHSIWybVEPFsPAVckAFvCj8VQv4hpr2//OoV0GFDje7nYCNDbPTK05P0DXu0NaOXNkATmnlm1N3SUhk+mvNI9gAk//t8EuhVNkQwT1QH29sHIBHYri7c8N7eF5Bi/ScbvLOQGjnIDqnwPnsou1uN79sAqywIDAQAB"
s1	rsa	1446	"k=rsa; t=s; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAo63N07Kl1y6nL/9wbGZY6o1Of0lekUTgaPIA70yACn3ing+emKJArcLmLiiGpur/sv6oUyCkL5E8E1mqOrzGg4IaWHvAasa7JiRLTHo8VerPTRm74D7eSJrA+akULvfxs5/fQ86wVwf5nF/van8WcQmNt4k8u8QcvZhEyEJHwbLToLHrvKkkgySuuS+cHyy71Q0ys" "T7voekJdMndzDFUFGuApNGqjk4/JJnF6hUUgdNm22GgWjuaI/oLg4z2dT9XviuHYkwhZ/9Us9yC5fTkP2eio8UvqoazTsKdYFYm7KVeVpaa/NHbjA8eIdglRxSrZBkdn4FIJsboqLDXV0zKhwIDAQAB"

Evidence

Domain Queried	DNS Record Type	Description	Value
remo.health	SPF	Sender Policy Framework	"v=spf1 include:_spfcf1.remo.health include:_spfcf2.remo.health include:_spfcf3.remo.health include:_spf.google.com include:spf.protection.outlook.com include:_spf.paubox.com -all"

Evidence

Software / Version	Category
Cloudflare	CDN

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.

Evidence

Software / Version	Category
PHP	Programming languages
Google Sign-in	Authentication
Google Cloud	IaaS
Amazon Web Services	PaaS
Cloudflare Bot Management	Security
LaunchDarkly	Feature management
HSTS	Security
Google Cloud CDN	CDN
Cloudflare	CDN
Amazon S3	CDN
HTTP/3	Miscellaneous

Vulnerability description

We noticed that server software and technology details are exposed, potentially aiding attackers in tailoring specific exploits against identified systems and versions.

Risk description

The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.

Recommendation

We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating system: HTTP server headers, HTML meta information, etc.